SAP Online Portal

Latest SAP News, Solutions, Error Codes, Help Files, Jobs, Documentations, Articles

SAP trex writer already open failed to create jacket filer CabinetException in Stapler.cpp

Case

In TREX, during daily operation for example indexing, you get the following error:

ERROR: writer already open
[1201441088] 2010-04-29 15:47:22.386 e TrexCabinet Stapler.cpp(01821) :ERROR: failed to create jacket!!!
[1201441088] 2010-04-29 15:47:22.386 e TrexCabinet Stapler.cpp(01822) :TrexCabinetException in Stapler.cpp(180): ‘failed to create filer!!!’

Solution

Change the value of parameter merge_deltas to “no” in TREXIndexServer.ini.

Following this, restart TREX and execute reindexing once more

Leave a Reply

Your email address will not be published.

Related topics

ORA-12906: cannot drop default temporary tablespace

Case During dropping psaptemp you get ORA-12906 error Solution First create another temporary tablespace for example temp2 SQL> CREATE TEMPORARY TABLESPACE temp2 TEMPFILE ‘/oracle/SM5/sapdata3/temp_2/temp2.data1’ SIZE […]

No main memory available twrtab reached memory limit during tp

Case: During Client import you get an error something like that: No main memory available (42500000) twrtab reached memory limit; memory usage 42000000 139596 entries […]

Could not obtain version info from start service in sum

Case in SAP Java Application Server you are applying patches via SUM and getting following error: Error getting the supported web methods. com.sun.xml.internal.ws.client.ClientTransportException: HTTP transport […]

Execution of the command *.db6_update_db.sh.* enable_roles finished with status TST_ERROR

You install Sap System with DB2 and get following error during executing db2 script residing in installation directory ERROR 2013-01-29 08:13:19.747 [sixxcstepexecute.cpp:937] FCO-00011 The step […]

SQL1641N The db2start command failed on sap server

Case You are installing a sap server with DB2 database on Unix/Linux System. During executing db2 binaries, for example db2start you get following error: SQL1641N […]