sqlcode is: -903 ORA-00903: invalid table name
Moderators: chulett, rschirm, roy
sqlcode is: -903 ORA-00903: invalid table name
I am unable to load the data in one of my target table ETL_ERROR_STAGING.It is throwing the error 'EtlErrorFileStagingOra: GenericQuery:esqlErrorHandler
Prepare failed for:
query is: select * from .ETL_ERROR_FILE_STAGING
sqlcode is: -903
esql complaint: ORA-00903: invalid table name,.I am using oracle enterprie stage with options LOAD&APPEND.I am able to insert the data when i tried to do it through TOAD.Could you please suggest me the solution if any one of you ever faced the same issue before?
Prepare failed for:
query is: select * from .ETL_ERROR_FILE_STAGING
sqlcode is: -903
esql complaint: ORA-00903: invalid table name,.I am using oracle enterprie stage with options LOAD&APPEND.I am able to insert the data when i tried to do it through TOAD.Could you please suggest me the solution if any one of you ever faced the same issue before?
Rajesh Peddi
Re: sqlcode is: -903 ORA-00903: invalid table name
And it is working fine when i used insert statemenet using upsert mode.peddidsx wrote:I am unable to load the data in one of my target table ETL_ERROR_STAGING.It is throwing the error 'EtlErrorFileStagingOra: GenericQuery:esqlErrorHandler
Prepare failed for:
query is: select * from .ETL_ERROR_FILE_STAGING
sqlcode is: -903
esql complaint: ORA-00903: invalid table name,.I am using oracle enterprie stage with options LOAD&APPEND.I am able to insert the data when i tried to do it through TOAD.Could you please suggest me the solution if any one of you ever faced the same issue before?
Rajesh Peddi
If you use these options in the Oracle enterprise stage you will have to give the table name only in the property Table=I am using oracle enterprie stage with options LOAD&APPEND.
And it is not possible to use
and that to it is a select, not an insert sqlquery is: select * from .ETL_ERROR_FILE_STAGING
Please check in your target stage..
Thanks,
Mohan.A.Jasti.
Mohan.A.Jasti.
Jasti,Jasti wrote:If you use these options in the Oracle enterprise stage you will have to give the table name only in the property Table=I am using oracle enterprie stage with options LOAD&APPEND.
And it is not possible to useand that to it is a select, not an insert sqlquery is: select * from .ETL_ERROR_FILE_STAGING
Please check in your target stage..
This is what it is little bit confusing.I am using LOAD&APPEND only,but still throwing me the error with select query.Thanks
Rajesh Peddi
The error was thrown at the stage EtlErrorFileStagingOra'EtlErrorFileStagingOra: GenericQuery:esqlErrorHandler
If that is one of your source stages..then check the select query..
chulett wrote:".ETL_ERROR_FILE_STAGING" is indeed an invalid table name. Either ensure the owner schema is provided or get rid of the dot. ...
Thanks,
Mohan.A.Jasti.
Mohan.A.Jasti.
No, It is a target table and table name is ETL_ERROR_FILE_STAGING.There is no dot in front of it.Jasti wrote:The error was thrown at the stage EtlErrorFileStagingOra'EtlErrorFileStagingOra: GenericQuery:esqlErrorHandler
If that is one of your source stages..then check the select query..chulett wrote:".ETL_ERROR_FILE_STAGING" is indeed an invalid table name. Either ensure the owner schema is provided or get rid of the dot. ...
Rajesh Peddi
Chulett,chulett wrote:Exactly - what changed? And as Ray would note, "nothing" is not the correct answer. And if you know it wasn't the job...
When i tried to view the log file..i could not even find it in scratch and it is not even generating the log file or control file where i can dig through.I contacted DBA to check if any schema updates happened on their end.What i am afraid of is in the exact error it is saying .ETL_ERROR_FILE_STAGING where schema name is empty.It should be schema_name.table_name...right?
Rajesh Peddi
As I noted earlier, and completely irrespective of DataStage, that leading dot your posted message showed is indeed invalid. You either need to ensure the schema is there before the dot, which makes it an 'absolute path' in a manner of speaking or you need to not have the dot. That would make it equivalent to a 'relative path', meaning Oracle will first look for a private synonym and then a public synonym for that name to know where to go. Failing that it will look for the table in the current / logged in user's schema.
It can't do any of that when the first thing it sees is a dot.
It can't do any of that when the first thing it sees is a dot.
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
Surprsingly , It is working fine when i tried to give the fully qualified name.But till yesterday it is with the table name only.Any how thanks chulett and all for your valuable suggestions.Thankschulett wrote:As I noted earlier, and completely irrespective of DataStage, that leading dot your posted message showed is indeed invalid. You either need to ensure the schema is there before the dot, which makes it an 'absolute path' in a manner of speaking or you need to not have the dot. That would make it equivalent to a 'relative path', meaning Oracle will first look for a private synonym and then a public synonym for that name to know where to go. Failing that it will look for the table in the current / logged in user's schema.
It can't do any of that when the first thing it sees is a dot.
Rajesh Peddi