CA IDMS SQL Quick Bridge error DB005138 Table OOAK-012 Not Found in Catalog
Article ID: 126445
Updated On:
Products
IDMS
IDMS - Database
IDMS - ADS
Issue/Introduction
SQL Quick Bridge may not connect to the desired target dictionary on the mainframe. If the connection fails, the error pop-up window may show these details:
Function: GetSchemanames
Statement: SQLExecDirect
DB005138 Table <dictname>.OOAK-0012 not found in catalog
Function: GetSchemanames
Statement: SQLExecDirect
DB005138 Table <dictname>.OOAK-0012 not found in catalog
Environment
This can occur in any IDMS environment where IDMS SQL QuickBridge is being deployed to access mainframe network schemas.
Resolution
The remedy to these errors is to issue the following commands in OCF:
CONNECT TO <DBname>;
CREATE SCHEMA <DBname> FOR NONSQL SCHEMA SYSDIRL.IDMSNTWK DBNAME <DBname>;
The value for <DBname> in these statements will be the target Dbname you're trying to access.
These statements will need to be repeated for every DBname that you want to access via QuickBridge.
QuickBridge can be used to access network schemas, subschemas, and records, and to generate a table procedures to access them. However, Table Procedures should be used only in a case of last resort. Accessing network records through direct SQL is MUCH more efficient. and on 19.0 the feature of Virtual Foreign keys will allows users to do a lot more with network records using direct SQL than was possible previously. With Virtual Foreign Keys the need to table Procedures had been greatly reduced.
CONNECT TO <DBname>;
CREATE SCHEMA <DBname> FOR NONSQL SCHEMA SYSDIRL.IDMSNTWK DBNAME <DBname>;
The value for <DBname> in these statements will be the target Dbname you're trying to access.
These statements will need to be repeated for every DBname that you want to access via QuickBridge.
QuickBridge can be used to access network schemas, subschemas, and records, and to generate a table procedures to access them. However, Table Procedures should be used only in a case of last resort. Accessing network records through direct SQL is MUCH more efficient. and on 19.0 the feature of Virtual Foreign keys will allows users to do a lot more with network records using direct SQL than was possible previously. With Virtual Foreign Keys the need to table Procedures had been greatly reduced.
Additional Information
As an alternative to using Table Procedures, for more information about using Virtual Foreign Keys check out these sources:
https://docops.ca.com/ca-idms/19/en/release-notes/new-features-and-enhancements#NewFeaturesandEnhancements-VirtualForeignKeys
https://docops.ca.com/ca-idms-ref/19/en/sql-reference/accessing-network-defined-databases/sql-virtual-keys
https://docops.ca.com/ca-idms-ref/19/en/sql-reference/accessing-network-defined-databases/sql-virtual-keys
https://docops.ca.com/ca-idms/19/en/release-notes/new-features-and-enhancements#NewFeaturesandEnhancements-VirtualForeignKeys
https://docops.ca.com/ca-idms-ref/19/en/sql-reference/accessing-network-defined-databases/sql-virtual-keys
https://docops.ca.com/ca-idms-ref/19/en/sql-reference/accessing-network-defined-databases/sql-virtual-keys
Feedback
Yes
No
Powered by
