If you are unable to create a new account, please email support@bspsoftware.com

 

News:

MetaManager - Administrative Tools for IBM Cognos
Pricing starting at $2,100
Download Now    Learn More

Main Menu

Cognos content manager issues and cursor inactive error

Started by cgb, 18 May 2017 09:20:03 PM

Previous topic - Next topic

cgb

We are getting following error when running reports.
Reports were working fine before 2 months. Suddenly getting below errors.


1) CM-SYS-5003 Content Manager is unable to connect to the content store. Verify that the database connection properties in the configuration tool are correct and that when you test the connection, the test is successful.ORA-01652: unable to extend temp segment by 128 in tablespace TEMP2 


2) RSV-DST-0014 Unable to deliver the output of the report.
See the run history details for more information. Ensure that the required services are started.
Ensure that the user account is configured to distribute the output in the requested manner.

3)  Copy operation failed when we tried to copy report from one folder to other folder.

CM-SYS-5006 Content Manager is unable to process your request because an unexpected event occurred in the content store database subsystem.ORA-01652: unable to extend temp segment by 128 in tablespace TEMP2

4) Other issues like copy paste operation not working. Cognos admin page not fully loading. Error while publishing package "BMT-MDC-0001 Unable to publish."

5) UDA-SQL-0114 The cursor supplied to the operation "sqlOpenResult" is inactive. UDA-SQL-0107 A general exception has occurred during the operation "open result". UDA-SQL-0107 A general exception has occurred during the operation "AOpen". ERROR:

6) object name ABC has name conflict with security view ABC..Checked model.xml file but there was no duplicate

Database team is going to increase space from there side.

Do we need to change configuration settings in cognos? If yes then which are those

MFGF

Quote from: cgb on 18 May 2017 09:20:03 PM
We are getting following error when running reports.
Reports were working fine before 2 months. Suddenly getting below errors.


1) CM-SYS-5003 Content Manager is unable to connect to the content store. Verify that the database connection properties in the configuration tool are correct and that when you test the connection, the test is successful.ORA-01652: unable to extend temp segment by 128 in tablespace TEMP2 


2) RSV-DST-0014 Unable to deliver the output of the report.
See the run history details for more information. Ensure that the required services are started.
Ensure that the user account is configured to distribute the output in the requested manner.

3)  Copy operation failed when we tried to copy report from one folder to other folder.

CM-SYS-5006 Content Manager is unable to process your request because an unexpected event occurred in the content store database subsystem.ORA-01652: unable to extend temp segment by 128 in tablespace TEMP2

4) Other issues like copy paste operation not working. Cognos admin page not fully loading. Error while publishing package "BMT-MDC-0001 Unable to publish."

5) UDA-SQL-0114 The cursor supplied to the operation "sqlOpenResult" is inactive. UDA-SQL-0107 A general exception has occurred during the operation "open result". UDA-SQL-0107 A general exception has occurred during the operation "AOpen". ERROR:

6) object name ABC has name conflict with security view ABC..Checked model.xml file but there was no duplicate

Database team is going to increase space from there side.

Do we need to change configuration settings in cognos? If yes then which are those

Hi,

This is an error from Oracle, which I assume you must be using for your content store database? The important part of the message is:

ORA-01652: unable to extend temp segment by 128 in tablespace TEMP2

Googling this error shows it's usually caused by one of two things - either your tablespace in Oracle isn't set to autoextend, or else the filesystem is full so Oracle has no more space to extend into?

See the below post from an Oracle forum:

https://community.oracle.com/message/14185964#14185964

Either way, the root cause of this is Oracle, so you're going to have to look there to fix the issue.

Cheers!

MF.
Meep!