Symptom
- Error: Cannot import the metadata table <name=AL_SETOPTIONS>.
- Migration from Oracle to SQL Server
- Table <Table Name.AL_SETOPTIONS> cannot be import for datastore <Datastore Name>. Possible causes: (1) Table do not exist in the database; (2) Information for import was specified incorrectly. Check the import information and try again. If the name is case-sensitive in the database (and not all uppercase), enter the name as it appears in the database and use double-quotation marks around the name to preserve the case. (BODI-1112339)
-
(14.2) 10-01-19 08:18:04 (R) (0640:3424) DBS-070404: |Data flow DF_Intro_collection|Reader AL_SETOPTIONS2
SQL submitted to ODBC data source <Data Source> resulted in error <[Microsoft][SQL Server Native Client 11.0][SQL Server]Invalid
object name '<Object>.AL_SETOPTIONS'.>. The SQL submitted is <SELECT "AL_SETOPTIONS"."PARENT_OBJID" FROM
"<Object>"."AL_SETOPTIONS" "AL_SETOPTIONS" WHERE ((((((( "AL_SETOPTIONS"."OPTION_NAME" = 'job_monitor_sample_rate') or (
"AL_SETOPTIONS"."OPTION_NAME" = 'Parallelism_degree')) or ( "AL_SETOPTIONS"."OPTION_NAME" = 'Cache_type')) or (
"AL_SETOPTIONS"."OPTION_NAME" = 'job_collect_statistics')) or ( "AL_SETOPTIONS"."OPTION_NAME" =
'job_collect_statistics_monitor')) or ( "AL_SETOPTIONS"."OPTION_NAME" = 'job_use_statistics')) or (
"AL_SETOPTIONS"."OPTION_NAME" = 'job_enable_dataquality')) >.
Read more...
Environment
- SAP Information Platform Services 4.x
- SAP Data Services 4.x
- Oracle
- SQL Server
Product
Keywords
bods, ds, sql, queries, changes, migration, DB, AL_, jobs, ATL, copied , KBA , EIM-DS-SVR , Administration/Server , Problem
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.
SAP Knowledge Base Article - Preview