cancel
Showing results for 
Search instead for 
Did you mean: 

ERROR: CANNOT_CREATE_COFILE

Former Member
0 Kudos

hi to all,

i have some serious query pls help me to solve it....

i successfully done client copy from PRD to SANDBOX.also update kernel patch @ sandbox.

but when i am update appl or other patch level then SPAM give me below error..

ERROR: CANNOT_CREATE_COFILE

Return Code-8

ERROR MESSAGE : OCS PACKAGE : SAPKB70014

I allready check permission to /usr/sap/trans/cofiles and data directory and its ok.

pls tell me what i missing....

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Check if the files you want to extract to the directories data and cofiles already exist because another sidadm in that transport domain already extracted them.

If that is the case you don't need to extract the files any more. Just use SPAM to upload all patches from the application server and you should have the support packages available in the SPAM.

Also check that the group sapsys has write permissions for the data and cofiles directories. Permissions 755 might restrict the sandbox user from creating any files. Try 775 instead (if not already done).

Kind regards,

Former Member
0 Kudos

Are you uploading the support pack from SAPGUI? You sure tha /usr/sap/trans is mounted correctly with read/write access on your sandbox? Logon to OS level as your sandbox <SID>adm and try to create a dummy file under /usr/sap/trans/cofiles and /usr/sap/trans/data

Former Member
0 Kudos

i successfully created files manualy... there is no permission realated problem

pls help me to solve out my problem

thx for your reply

Former Member
0 Kudos

If you are sharing (may be) your trans directory between PROD and Sandbox then can you upload the application patch from your production server and see what happen. Don't worry you are just uploading the file this will not apply to your production.

Former Member
0 Kudos

Still Same problem.....

thx for your reply

Former Member
0 Kudos

Ok, can you manually unpack the file (SAPCAR -xvf <file_name>.SAR) and copy R.SAP to the data and K.SAP cofiles?

To visible in SPAM do SPAM --> support package --> load from application server.

Former Member
0 Kudos

1. From which folder shall i do copy R.SAP to the data and K.SAP cofiles ??

2. I am already visible to the patch which we want to update still getting "DISSAMBLE" error mentioned earlier.

Former Member
0 Kudos

opps! something went wrong in previous reply. Sorry.

copy your support pack file on to UNIX server, you can copy may be to your <SID>adm user's home directory.

then perform following:

SAPCAR -xvf <support_packfile.SAR> this will create a directory as EPS/in and file name will be .PAT

Just copy the .PAT file to your /usr/sap/trans/EPS/in

and refresh your SPAM as mentioned above.

Former Member
0 Kudos

Please find below results of SAPCAR we executed for patch updation, in SPAM we can find patches KH60011 & KH60012 but while importing queue getting error.

GPR3PRD:gppadm 3> SAPCAR -xvf KH60011.SAR

SAPCAR: processing archive KH60011.SAR (version 2.01)

x EPS/in/CSN0120061532_0028288.ATT

x EPS/in/CSN0120061532_0028288.PAT

SAPCAR: 2 file(s) extracted

GPR3PRD:gppadm 4> SAPCAR -xvf KH60012.SAR

SAPCAR: processing archive KH60012.SAR (version 2.01)

x EPS/in/CSR0120031469_0029698.ATT

x EPS/in/CSR0120031469_0029698.PAT

SAPCAR: 2 file(s) extracted

Former Member
0 Kudos

Now you need to copy below files to /usr/sap/trans/EPS/in

EPS/in/CSN0120061532_0028288.ATT

EPS/in/CSN0120061532_0028288.PAT

EPS/in/CSR0120031469_0029698.ATT

EPS/in/CSR0120031469_0029698.PAT

Then in SPAM you need to load SPAM--> support package --> from application server

Former Member
0 Kudos

we already do this step.....

when we import in queue it getting same error

Former Member
0 Kudos

can you do following and paste the output.

ls -l /usr/sap/trans

ls -l /usr/sap/trans/data

ls -l /usr/sap/trans/cofiles

df -k /usr/sap/trans

Former Member
0 Kudos

There are so many files in data and cofiles directory,,,,, which is bit difficult to paste here whole output.

Former Member
0 Kudos

fine execute each command with below option at the end. mean only page.

| more

Former Member
0 Kudos
  1. df -g /usr/sap/trans

Filesystem GB blocks Free %Used Iused %Iused Mounted on

/dev/sapworklv 50.00 16.55 67% 38784 1% /usr/sap

#

Former Member
0 Kudos
  1. df -g /usr/sap/trans

Filesystem GB blocks Free %Used Iused %Iused Mounted on

/dev/sapworklv 50.00 16.55 67% 38784 1% /usr/sap

#

Former Member
0 Kudos

what about

ls -l /usr/sap/trans

Former Member
0 Kudos

hi

After Client copy have you checked STMS and did you reconfigured STMS

some time which will show you inconsistent so you have to delete stms and reconfigure it

then you would get proper cofile and data files

Regards

krishna

Former Member
0 Kudos

Hi,

Go STMS --> Overview > System select the Sandbox system and click from Menu on SAP System> check

and check whether all your test results are fine.

If issues, pls. check or post here

Regards,

Rajesh

Former Member
0 Kudos

dear rajesh,

when I Go STMS --> Overview --> System , i see two system there

one is sandbox system and onther one is virtual system

when i check sandbox system its give successful conection test but when i check virtual system its told me its a virtual system

still problem is not solve

waiting for your reply

thx....

Former Member
0 Kudos

Can you create a dummy transport in sandbox and try to release and see the result. Whether the transport creates a data/cofiles or not.

Former Member
0 Kudos

"when i check sandbox system its give successful conection test " I was not asking only connection test,

Perform below checks and see the results,

1. Connection test

2. Transport Diectory

3. Transport Tool

Let us know if any errors

Regards,

Rajesh