Quantcast
Channel: SCN: Message List
Viewing all articles
Browse latest Browse all 2175

Re: SQL submitted to ODBC resulted in an error

$
0
0

Hi Dirk Venken,

 

 

So I created the first two data flows in one work flow and created a separate work flow to join the output from first two data flows and below is the error message-

 

 

 

|Data flow F4211LA|Loader Query_STG_F4211LA

                                                       ODBC data source <UKNWSRBKG402> error message for operation <SQLExecute>: <[Microsoft][SQL Server Native Client 10.0][SQL

                                                       Server]Invalid object name 'DBO.STG_F4211LA'.>.

|Data flow F4211LA|Loader Query_STG_F4211LA

                                                       Execution of <Regular Load Operations> for target <STG_F4211LA> failed. Possible causes: (1) Error in the SQL syntax; (2)

                                                       Database connection is broken; (3) Database related errors such as transaction log is full, etc.; (4) The user defined in the

                                                       datastore has insufficient privileges to execute the SQL. If the error is for preload or postload operation, or if it is for

                                                       regular load operation and load triggers are defined, check the SQL. Otherwise, for (3) and (4), contact your local DBA.

|Data flow F42119LA|Loader Query_ST_F42119LA

                                                     ODBC data source <UKNWSRBKG402> error message for operation <SQLExecute>: <[Microsoft][SQL Server Native Client 10.0][SQL

                                                     Server]Invalid object name 'DBO.ST_F42119LA'.>.

  |Data flow F42119LA|Loader Query_ST_F42119LA

                                                     Execution of <Regular Load Operations> for target <ST_F42119LA> failed. Possible causes: (1) Error in the SQL syntax; (2)

                                                     Database connection is broken; (3) Database related errors such as transaction log is full, etc.; (4) The user defined in the

                                                     datastore has insufficient privileges to execute the SQL. If the error is for preload or postload operation, or if it is for

                                                     regular load operation and load triggers are defined, check the SQL. Otherwise, for (3) and (4), contact your local DBA.


Viewing all articles
Browse latest Browse all 2175

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>