Thanks, that's handy to know about the Truncate option. I will
definitely be trying that as one task would be simpler.
Yes, the automated task is the same account as what I use when I run
it manually in the morning.
Here is some more info though. I am seeing errors that I am sure are
releated.
In the nmi.log I see the following error a lot:
Fatal NI connect error 12560, connecting to:
(DESCRIPTION=(ADDRESS=(PROTOCOL=BEQ)(PROGRAM=ORACLE)(ARGV0=ORACLETEST)(ARGS='(DESCRIPTION=(LOCAL=YES)(ADDRESS=(PROTOCOL=beq)))'))(CONNECT_DATA=(CID=(PROGRAM=E:\oracle\ora81\bin\dbsnmp.exe)(HOST=ESC-AD-ORAWEB1)(USER=SYSTEM))))
VERSION INFORMATION:
TNS for 32-bit Windows: Version 8.1.7.0.0 - Production
Oracle Bequeath NT Protocol Adapter for 32-bit Windows: Version
8.1.7.0.0 - Production
Windows NT TCP/IP NT Protocol Adapter for 32-bit Windows: Version
8.1.7.0.0 - Production
Time: 11-MAR-2003 09:21:48
Tracing not turned on.
Tns error struct:
nr err code: 0
ns main err code: 12560
TNS-12560: TNS:protocol adapter error
ns secondary err code: 0
nt main err code: 530
TNS-00530: Protocol adapter error
nt secondary err code: 2
nt OS err code: 0
and in the sqlnet.log I see:
Fatal NI connect error 12640, connecting to:
(DESCRIPTION=(LOCAL=YES)(ADDRESS=(PROTOCOL=beq)))
VERSION INFORMATION:
TNS for 32-bit Windows: Version 8.1.7.0.0 - Production
Oracle Bequeath NT Protocol Adapter for 32-bit Windows: Version
8.1.7.0.0 - Production
Time: 11-MAR-2003 09:22:18
Tracing not turned on.
Tns error struct:
nr err code: 0
ns main err code: 12640
TNS-12640: Authentication adapter initialization failed
ns secondary err code: 0
nt main err code: 0
nt secondary err code: 0
nt OS err code: 0
"FC" <flavio_at_tin.it> wrote in message news:<815aa.28332$zo2.788285_at_news2.tin.it>...
> First of all it is possible to specify the TRUNCATE option directly in the
> SQL*Loader control file, so, unless you have very special requirements,
> there is no need to truncate the table in a separate script. If data volumes
> are nearly constant over time, I strongly encourage you to use the truncate
> option instead of running two scripts.
>
> Assuming you have such special requirements, the error you get may be caused
> by an authentication problem caused by the user specified in the task
> scheduler.
> When you run the job in the morning, are you running it under the same
> account?
>
> Bye,
> Flavio
Received on Tue Mar 11 2003 - 08:27:20 CST
