Unlocking tables after fastload failure

Tools
Enthusiast

Unlocking tables after fastload failure

Is there a way other than dropping and recreating the load tables after the Fastload failed.
If so can some one give me the syntax? Your help would be highly appreciated. I tried to run
Begin Loading .... and End Loading and it didn't help. See below the syntax I used.

Krishna.R
############## SYNTX USED #######################

.logon oneview/sysdba,
BEGIN LOADING paperdb.account_STG errorfiles load_work.temp_ER1 ,load_work.temp_ER2;
END LOADING;

################ OUTPUT ########################

0001 .logon oneview/sysdba,

**** 15:25:07 Current CLI or RDBMS allows maximum row size: 64K

**** 15:25:07 Character set for this job: ASCII

**** 15:25:42 CLI Error 301: CLI2: SESSOVER(301): Exceeded max number

of sessions allowed.

**** 15:25:43 Number of FastLoad sessions connected = 298

**** 15:25:43 FDL4808 LOGON successful

FastLoad - Enter your command:

BEGIN LOADING paperdb.account_STG errorfiles load_work.temp_ER1 ,load_work.temp_ER2;

0002 begin loading papex_load_tb.account_affinity_STG errorfiles prod_work

.srini_ER1 ,prod_work.srini_ER2;

**** 15:26:11 RDBMS error 2635: Error tables are invalid OR

ACCOUNT_AFFINITY_STG is in an invalid state for Load -
FastLoad - Enter your command:

###############################################
2 REPLIES
Enthusiast

Re: Unlocking tables after fastload failure



Please see this other thread on the same subject....

http://www.teradata.com/teradataForum/shwmessage.aspx?forumid=10&messageid=2703
Enthusiast

Re: Unlocking tables after fastload failure

Thanks Dennis, I will follow up with the other post.

Krishnan.R