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

Reconcile failure : Unale to write e List Item

Started by aa2288, 18 Nov 2009 11:07:11 AM

Previous topic - Next topic

aa2288

hi,

I am getting the error Unale to write e List Item. Looked at Cognos documentation . It says that the Tablespace is out of Memory. But I am using SQL server as a database. Does this mean that we need more Job Servers?

Problem(Abstract)
An error occurs when running a GTP on an application. 
 
Symptom
Error Number: 3219
Line Number: 400
Description: Unable to execute Job Item
Unable to write data for e.List item {3D531333-B683-44CF-AD99-BEDB947FF5E1} using 'epRT_%v.AdminServer.WriteReconciledData'

Operation is not allowed in this context.

 



Cause
The tablespace was running out of space, and needed to have its allocation increased. 
 

Environment
Oracle 
 

Resolving the problem
Have the DBA check the tablespace in Oracle then adjust allocation of space, where necessary. 
 


Related information
1020761 -- When running a macro that runs a reconcile it fails 1011768 -- Reconcile cancels on first GTP of new application: Operation is not allowed in this context

 


 

Historical Number


Dan Stroebel

Looks to me as if you were running out of space on the database server.

\dan

mizu

i would check the followings:
- is there enough space on the database server
- if running gtp again could resolve the problem
- if the application is assigned to a job server

SomeClown

Sometimes happens for one of the following (no guarantee any apply in your situation):

-virus scanner grab temp files and don't release in time
-it's a vm and insufficient resources not available exactly when needed
-db server is overloaded or busy with other processes
-network hiccup causes loss of security context or db connectivity


If it were space in SQL Server, you'd see a message in the planningerrorlog.csv on the job server that mentioned it - planning will catch the error code returned by sql (usually).

Version you're running? 

You may also want to find the elist item in question and if clientside reconcile is allowed, manually open the elist item to see if it will reconcile that way

aa2288

Thanks for the pointers . I am running Cognos 8.2 and SQL server 2005. Running the GTP again solves the issue but issue is recurring in nature. All E List items are not being successfully reconciled at one go.Planning to add one more Job Server .hope it may help.

SomeClown

8.2 was a pretty buggy planning release - I would recommend moving up to a newer release - 8.3 if you don't want to change much, 8.4 if you want the new client.  Most clients moved off 8.2 pretty quick.

If you're adding another job server by adding a VM from the same esx host, that may not help since one issue would be the amount of host resources made available to the VM images.  If it's physical, you may want to think about installing 8.3 to that one and pull your 8.2 up to 8.3.

aa2288

The Job servers are physical not running on VM. Yup theere are lota issues with 8.2.

doyler2000

Hey - similar problem - how often do you restart Admin and Job Servers? I got rid of these errors by restarting every night... brings its own problems but worth a go.. something to do with contiguous memory (spelt correct??)

N