Bulk load to oracle
in [SAS]
|
From: chowdary on 4 Jan 2010 06:04 Hi, proc sql; 24 insert into ikd.'IKD$TA_F_PERLE'n (BULKLOAD=YES BL_LOG='/ pkg/moip/tmv824/sas_datamart/sasbin/t2DISK' 24 ! BL_DELETE_DATAFILE=YES OR_PARTITION=P200907) 25 select * from ikdb.loadperle3; NOTE: 2 rows were inserted into IKD.'IKD$TA_F_PERLE'n. ERROR: The SQL*Loader utility failed to execute(OS RC=1). Some possible reasons: -SQLLDR not installed.The cmd assumed is "sqlldr". If it is anything else use BL_SQLLDR_PATH to specify it. -SQLLDR may be having trouble creating the log file.Make sure you have write permission to the dir where the log is created(default is current dir) If BL_LOG is specified, make sure the path specified is a valid one. -Remove any double sets of quotes you may be having-keep only one set. *********But Sqlldr is being installed *********And I have write permissions to particula table. Can Any one solve plz ?
From: Arthur Tabachneck on 4 Jan 2010 07:55 Chowdary, One possibility is that the log you specified isn't the one you intended. Have you tried it using the full path rather than: '/pkg/moip/tmv824/sas_datamart/sasbin/t2DISK' ? Art ------------ On Jan 4, 6:04 am, chowdary <aramakrishna.chowd...(a)gmail.com> wrote: > Hi, > > proc sql; > 24 insert into ikd.'IKD$TA_F_PERLE'n (BULKLOAD=YES BL_LOG='/ > pkg/moip/tmv824/sas_datamart/sasbin/t2DISK' > 24 ! BL_DELETE_DATAFILE=YES OR_PARTITION=P200907) > 25 select * from ikdb.loadperle3; > NOTE: 2 rows were inserted into IKD.'IKD$TA_F_PERLE'n. > > ERROR: The SQL*Loader utility failed to execute(OS RC=1). Some > possible reasons: > -SQLLDR not installed.The cmd assumed is "sqlldr". If it is anything > else use BL_SQLLDR_PATH to specify it. > -SQLLDR may be having trouble creating the log file.Make sure you > have write permission to the dir where the log is > created(default is current dir) If BL_LOG is specified, make > sure the path specified is a valid one. > -Remove any double sets of quotes you may be having-keep only one > set. > > *********But Sqlldr is being installed > *********And I have write permissions to particula table. > > Can Any one solve plz ?
From: Michael Davis on 5 Jan 2010 10:51 Hello Chowdary, Here are the data set options that I use at our site to bulkload SAS data sets into Oracle: (BULKLOAD=YES BL_OPTIONS='ERRORS=899,ROWS=50000') I typically use a DATA Step instead of PROC SQL to load SAS data into Oracle but that should matter all that much. As an aside, if you have an urgent problem, consider contacting SAS Tech Support. I have gotten very good help and prompt attention on questions to the SAS/ACCESS - Oracle queue. Best wishes to you and everyone else on the SAS-L list for 2010. - Michael Davis On Mon, January 4, 2010 6:04 am, chowdary <aramakrishna.chowdary(a)GMAIL.COM>wrote: > Hi, > > proc sql; > 24 insert into ikd.'IKD$TA_F_PERLE'n (BULKLOAD=YES BL_LOG='/ > pkg/moip/tmv824/sas_datamart/sasbin/t2DISK' > 24 ! BL_DELETE_DATAFILE=YES OR_PARTITION=P200907) > 25 select * from ikdb.loadperle3; > NOTE: 2 rows were inserted into IKD.'IKD$TA_F_PERLE'n. > > ERROR: The SQL*Loader utility failed to execute(OS RC=1). Some > possible reasons: > -SQLLDR not installed.The cmd assumed is "sqlldr". If it is anything > else use BL_SQLLDR_PATH to specify it. > -SQLLDR may be having trouble creating the log file.Make sure you > have write permission to the dir where the log is > created(default is current dir) If BL_LOG is specified, make > sure the path specified is a valid one. > -Remove any double sets of quotes you may be having-keep only one > set. > > *********But Sqlldr is being installed > *********And I have write permissions to particula table. > > Can Any one solve plz ? > -- Michael L. Davis Ambler PA E-Mail: michael.davis(a)alumni.duke.edu
From: Eli Y. Kling on 6 Jan 2010 10:13 Just before the Jul vacation (for Sir Issac NewtonÂ’s Birthday) I was looking into improving the performance of writing to Oracle. In the set-up I was working within (generally sas 9.1, Unix and Oracle and sas are on the same switch) the Bulk Load did not improve performance and in certain instances slowed things down. The best improvement I got was with setting the INSERTBUFF dataset option to maximum (32767). You might want also to try setting DBCOMMIT to 0. However, I have literally just come out of a meeting where we redesigned the solution and that will cut down significantly on the data flowing back and forth between sas and Oracle. With regard, Eli
|
Pages: 1 Prev: 45 Degree reference line in PROC SGPLOT XXXX Next: PROC REPORT error |