IBM InfoSphere Metadata Asset Manager Timeout Error

Hi ,

Recently two of our clients had same problem, time out error.

When we try to import metadata of databases that we will investigate about personel data GDPR vise , we couldn’t import any tables.

On a SQL Server via ODBC Connector ;

CDIMR3801E Error Occurred when attempting to browse bridge or connector data CDIMR007E. There was an error querying all tables in the <SCHEMA_NAME> schema.

On an Oracle 12C db via Oracle Native Connector.

CDIMR3790E An error occurred while importing data from bridge or connector(CAS/OracleConnector__11).

The solution is the same.

If you use a Windows server for IBM Information Server go to the installation path. Check if timeout parameter set or not. Then you set time out parameter , in this example I set it to 5 minutes which is 300 seconds. But if you import thousands of data you can set it 50 minutes.

C:\IBM\InformationServer\ASBServer\bin>iisAdmin.bat -display -key cas.agent.timeout

C:\IBM\InformationServer\ASBServer\bin>iisAdmin.bat -set -key cas.agent.timeout -value 300

C:\IBM\InformationServer\ASBServer\bin>iisAdmin.bat -display -key cas.agent.timeout

Be careful when you set parameters , I accidently delete once iisAdmin.bat file. If you do that you need to find same file from other installed information server instances.

for more information;

InfoSphere Optim Error: Client-Side OCI Error id=OCI_NO_DATA

Hi ,

At one of our customer we are using InfoSphere Optim to archive old records for GDPR.

We create a parent-child hierarchy model of their database model.We will archive 3 million policy and connected other data about it.

Today when we deleting archived data from database which is oracle 11.2 , we get error like below at process report;

Delete Process Errors
	Data Base Error Detected in DEBUG_CORE.xx.xxxxxx_xxxx_xx:
		Client-Side OCI Error id=OCI_NO_DATA

This was an unfamiliar error to me, and when I do my research I couldn’t find anything about it.

There was no error on archive request , but we can’t complete delete request successfully.

After some research on database found a trigger on this table and it was blocking our deleting process.

So when you get an error like this , you can check your triggers first.

By the way you might need a delete fine tuning ;

for get detailed info ;