ERROR Unable to open the Job

A forum for discussing DataStage<sup>®</sup> basics. If you're not sure where your question goes, start here.

Moderators: chulett, rschirm, roy

Post Reply
lote11
Participant
Posts: 24
Joined: Fri Apr 15, 2011 8:10 am

ERROR Unable to open the Job

Post by lote11 »

Hello guys, im having this problem when i want to open any job (server or sequence).


Unable to open the Job

Unable to get EObject c2e76d84.43058877.4e410a86.76875176-b082-429c.a382.d10d3ed182c8
com.ibm.datastage.exception.DSException: Unable to get EObject c2e76d84.43058877.4e410a86.76875176-b082-429c.a382.d10d3ed182c8
at com.ascential.dstage.proxies.NewRepos.getEObjectCRLockWithID(NewRepos.java:1694)
at com.ascential.dstage.proxies.NewRepos.getEObjectCRLockWithID(NewRepos.java:1652)
Caused by: com.ibm.datastage.exception.DSException: Unable to get c2e76d84.43058877.4e410a86.76875176-b082-429c.a382.d10d3ed182c8
at com.ibm.datastage.repository.DSRepository.getEObjectCRLockCommon(DSRepository.java:592)
at com.ibm.datastage.repository.DSRepository.getEObjectCRLockWithID(DSRepository.java:499)
at com.ascential.dstage.proxies.NewRepos.getEObjectCRLockWithID(NewRepos.java:1671)
... 1 more
Caused by: com.ibm.datastage.exception.DSException: Unable to load RID - c2e76d84.43058877.4e410a86.76875176-b082-429c.a382.d10d3ed182c8
at com.ibm.datastage.repository.locking.LockerDelegateBase.loadByRidNoRef(LockerDelegateBase.java:199)
at com.ibm.datastage.repository.locking.LockingDelegate.loadByRidNoRef(LockingDelegate.java:77)
at com.ibm.datastage.repository.locking.LockerDelegateBase.loadByRidNoRef(LockerDelegateBase.java:108)
at com.ibm.datastage.repository.locking.LockingDelegate.loadByRidWithID(LockingDelegate.java:93)
at com.ibm.datastage.repository.DSRepository.getEObjectCRLockCommon(DSRepository.java:515)
... 3 more
Caused by: com.ascential.xmeta.exception.ServiceException: Error loading objects from list of rids
at com.ascential.xmeta.service.repository.RepositoryServiceSupport.loadByRid(RepositoryServiceSupport.java)
at com.ascential.xmeta.service.repository.RepositoryServiceSupport.loadEObjectMementos(RepositoryServiceSupport.java)
at com.ascential.xmeta.service.repository.AbstractRepositoryLocalStatelessServiceBean.loadByRid(AbstractRepositoryLocalStatelessServiceBean.java)
at com.ascential.xmeta.shared.repository.core.EJSLocalStatelessSandboxLocalStatelessService_7aa4a3ce.loadByRid(Unknown Source)
at com.ascential.xmeta.service.repository.AbstractRepositoryRemoteStatefulServiceBean.loadByRid(AbstractRepositoryRemoteStatefulServiceBean.java)
at com.ascential.xmeta.shared.repository.core.EJSRemoteStatefulSandboxRemoteStatefulService_4baa4bb1.loadByRid(Unknown Source)
at com.ascential.xmeta.shared.repository.core._EJSRemoteStatefulSandboxRemoteStatefulService_4baa4bb1_Tie.loadByRid(_EJSRemoteStatefulSandboxRemoteStatefulService_4baa4bb1_Tie.java)
at com.ascential.xmeta.shared.repository.core._EJSRemoteStatefulSandboxRemoteStatefulService_4baa4bb1_Tie._invoke(_EJSRemoteStatefulSandboxRemoteStatefulService_4baa4bb1_Tie.java)
at com.ibm.CORBA.iiop.ServerDelegate.dispatchInvokeHandler(ServerDelegate.java)
at com.ibm.CORBA.iiop.ServerDelegate.dispatch(ServerDelegate.java)
at com.ibm.rmi.iiop.ORB.process(ORB.java)
at com.ibm.CORBA.iiop.ORB.process(ORB.java)
at com.ibm.rmi.iiop.Connection.respondTo(Connection.java)
at com.ibm.rmi.iiop.Connection.doWork(Connection.java)
at com.ibm.rmi.iiop.WorkUnitImpl.doWork(WorkUnitImpl.java)
at com.ibm.ejs.oa.pool.PooledThread.run(ThreadPool.java)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java)
Caused by: com.ascential.xmeta.repository.RepositoryException: Error loading objects from list of rids
at com.ascential.xmeta.repository.impl.AbstractDefaultRepository.loadByRid(AbstractDefaultRepository.java)
... 17 more
Caused by: com.ascential.xmeta.persistence.PersistenceException: com.ascential.xmeta.locking.LockManagerException: Persistence exception trying to store lock info
at com.ascential.xmeta.persistence.impl.basic.BasicPersistence.lockObjects_(BasicPersistence.java:2657)
at com.ascential.xmeta.persistence.impl.basic.BasicPersistence.acquireLocksOnObjects(BasicPersistence.java:802)
at com.ascential.xmeta.persistence.impl.basic.BasicPersistence.getByRid(BasicPersistence.java)
at com.ascential.xmeta.persistence.impl.basic.BasicPersistence.getByRid(BasicPersistence.java)
... 18 more
Caused by: com.ascential.xmeta.locking.LockManagerException: Persistence exception trying to store lock info
at com.ascential.xmeta.locking.impl.persistent.PersistentLockManager.addLockInfo(PersistentLockManager.java:559)
at com.ascential.xmeta.locking.impl.persistent.PersistentLockManager.lockObjectByRid(PersistentLockManager.java)
at com.ascential.xmeta.locking.impl.persistent.PersistentLockManager.lockObject(PersistentLockManager.java)
at com.ascential.xmeta.locking.impl.persistent.PersistentLockManager.lockObjects(PersistentLockManager.java)
at com.ascential.xmeta.persistence.impl.basic.BasicPersistence.lockObjects_(BasicPersistence.java:2647)
... 21 more
Caused by: com.ascential.xmeta.persistence.orm.PersistentEObjectPersistenceException: com.ascential.xmeta.persistence.orm.ObjectStorageException: com.ascential.xmeta.persistence.orm.ObjectStorageException: org.apache.ojb.broker.accesslayer.OJBBatchUpdateException: com.ibm.isf.jdbc.base.BaseBatchUpdateException: [IBM][SQLServer JDBC Driver][SQLServer]The transaction log for database 'XMeta' is full. To find out why space in the log cannot be reused, see the log_reuse_wait_desc column in sys.databases
at com.ascential.xmeta.persistence.orm.impl.ojb.OjbPersistentEObjectPersistence.add(OjbPersistentEObjectPersistence.java:577)
at com.ascential.xmeta.persistence.orm.impl.ojb.OjbPersistentEObjectPersistence.add(OjbPersistentEObjectPersistence.java:908)
at com.ascential.xmeta.locking.impl.persistent.PersistentLockManager.addLockInfo(PersistentLockManager.java:498)
... 25 more
Caused by: com.ascential.xmeta.persistence.orm.ObjectStorageException: com.ascential.xmeta.persistence.orm.ObjectStorageException: org.apache.ojb.broker.accesslayer.OJBBatchUpdateException: com.ibm.isf.jdbc.base.BaseBatchUpdateException: [IBM][SQLServer JDBC Driver][SQLServer]The transaction log for database 'XMeta' is full. To find out why space in the log cannot be reused, see the log_reuse_wait_desc column in sys.databases
at com.ascential.xmeta.persistence.orm.impl.ojb.OjbObjectPersistence.store(OjbObjectPersistence.java)
at com.ascential.xmeta.persistence.orm.impl.ojb.OjbObjectPersistence.add(OjbObjectPersistence.java:203)
at com.ascential.xmeta.persistence.orm.impl.ojb.OjbPersistentEObjectPersistence.add(OjbPersistentEObjectPersistence.java:574)
... 27 more
Caused by: com.ascential.xmeta.persistence.orm.ObjectStorageException: org.apache.ojb.broker.accesslayer.OJBBatchUpdateException: com.ibm.isf.jdbc.base.BaseBatchUpdateException: [IBM][SQLServer JDBC Driver][SQLServer]The transaction log for database 'XMeta' is full. To find out why space in the log cannot be reused, see the log_reuse_wait_desc column in sys.databases
at com.ascential.xmeta.persistence.orm.impl.ojb.OjbObjectPersistence.executeBatch(OjbObjectPersistence.java)
... 30 more
Caused by: org.apache.ojb.broker.accesslayer.OJBBatchUpdateException: com.ibm.isf.jdbc.base.BaseBatchUpdateException: [IBM][SQLServer JDBC Driver][SQLServer]The transaction log for database 'XMeta' is full. To find out why space in the log cannot be reused, see the log_reuse_wait_desc column in sys.databases
at org.apache.ojb.broker.accesslayer.ConnectionManagerImpl.executeBatch(Unknown Source)
... 31 more
Caused by: com.ibm.isf.jdbc.base.BaseBatchUpdateException: [IBM][SQLServer JDBC Driver][SQLServer]The transaction log for database 'XMeta' is full. To find out why space in the log cannot be reused, see the log_reuse_wait_desc column in sys.databases
at com.ibm.isf.jdbc.sqlserver.SQLServerImplStatement.getBatchRowsAffectedCount(Unknown Source)
at com.ibm.isf.jdbc.base.BasePreparedStatement.executeBatch(Unknown Source)
at com.ibm.isf.jdbcx.base.BaseStatementWrapper.executeBatch(Unknown Source)
at com.ibm.ws.rsadapter.jdbc.WSJdbcStatement.executeBatch(WSJdbcStatement.java)
at org.apache.ojb.broker.platforms.PlatformDefaultImpl.executeBatch(Unknown Source)
at org.apache.ojb.broker.util.batch.PreparedStatementInvocationHandler.doExecute(Unknown Source)
at org.apache.ojb.broker.util.batch.PreparedStatementInvocationHandler.invoke(Unknown Source)
at $Proxy8.doExecute(Unknown Source)
at org.apache.ojb.broker.util.batch.BatchConnection.executeBatch(Unknown Source)
... 32 more


any idea why this happen ?
Thanks.
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

I'd start with this message and your DBA:

[IBM][SQLServer JDBC Driver][SQLServer]The transaction log for database 'XMeta' is full. To find out why space in the log cannot be reused, see the log_reuse_wait_desc column in sys.databases
-craig

"You can never have too many knives" -- Logan Nine Fingers
lote11
Participant
Posts: 24
Joined: Fri Apr 15, 2011 8:10 am

Post by lote11 »

thanks, im working in erase the log. ill tell you if that works.
Juan Escalante
IT Consultant
greggknight
Premium Member
Premium Member
Posts: 120
Joined: Thu Oct 28, 2004 4:24 pm

Post by greggknight »

ERASE THE LOG?
hope you don't need to recover!

You should get with your DBA
If your transaction logs are filling up then most likely backups are not being done or they are definitly not being done frequently.

Is XMETA local on DB2 or on another server, Oracle or SQL server.
Either way you need to get some maintenance plans establised on all the datastage (related databases)
"Don't let the bull between you and the fence"

Thanks
Gregg J Knight

"Never Never Never Quit"
Winston Churchill
lote11
Participant
Posts: 24
Joined: Fri Apr 15, 2011 8:10 am

Post by lote11 »

the solution was erasing log!!

Thanks all!
Juan Escalante
IT Consultant
padma
Premium Member
Premium Member
Posts: 2
Joined: Thu Oct 28, 2004 3:29 pm

Hello, was going thorugh the post and I got the error, Unabl

Post by padma »

Hello sir, I was going through the post as I had some issue while saving a copy of a job in our datastage environment.

Error:
Unable to extent index (INDEX_NAME) by 128 in tablespace ISMETA_DATA
It is an issue in the database which I contacted our DBA on this.

I was also curious how did you erase the log for your issue?

Any info would be helpful
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

The answer to your question depends on where your logs are stored - in XMETA or the 'legacy' Universe repository... which is controlled by your RTLogging & ORLogging settings off the top of my head.

What version are you running?
-craig

"You can never have too many knives" -- Logan Nine Fingers
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

This is the database transaction log for the XMETA database, not DataStage job logs. In an ideal world a DBA monitors how full the transaction log is getting and truncates older entries before it becomes a problem.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

Oh, THAT log. Never mind. :wink:
-craig

"You can never have too many knives" -- Logan Nine Fingers
Post Reply