[QUESTION] File CONOTRL.SQL is not being created!!

[symon_braunbaer]

Dear experts,

I am doing a Java refresh from our production to our development system.

I have first restored the oracle 11 database. As it is NetWeaver 7.3 EHP1, it

should be possible to do a refresh or system copy using the backup/restore

method, which according to SAP is supported for v. 7.3.

Afterwards, I started SWPM for NetWeaver 7.3 in order to do a target system

installation, in order to manage the mess with the java IDs.

Though this installation is asking for a file, named CONTROLSQL or CONTROL.SQL

(both names are mentioned in different parts of the same screen!! How

confusing, dear SAP !!!)

Then at the bottom of this infamous window, there is an explanation, that the file

is being created during the source system export preparation.

Grrr, fine!! I went to the source system, inflated quickly another SWPM there, did

the export preparation and... GUESS WHAT !! No CONTROLSQL or CONTROL.SQL

file!! Nor in the install directory (which I have separate - not /tmp), neither in the

export location. And I even searched in /tmp and nothing like this !!

Now I am exporting the entire source system while it is running !! (can't shutdown

the production!). Where is this file pleasseeeeee...???

I have done the same procedure on another project with MSSQL Server and it

went flawlessly without any control sql-files!!

Thanks a lot for your help!!

[Reagan · Accepted solution]

Hello Symon

The CONTROL.SQL is created by the OraBRCopy Java tool (ORABRCOPY.SAR) and it is mentioned in the system copy guide.

The procedure to create the CONTROL.SQL is mentioned in the guide.

Please check the guide.

https://websmp101.sap-ag.de/~sapidb/011000358700001324482012E

https://websmp101.sap-ag.de/~sapidb/011000358700000877172012E

Regards

RB

[symon_braunbaer · Accepted solution]

Thank you Reagan,

I have awarded you with the correct answer, though unfortunately this is

not a solution for my problem...

According to the system copy guide, which you sent me (thanks for the

links, you saved me a few minutes for searching!)

1) The OraBRCopy tool restarts the database, so it is not an online operation.

2) The Backup/restore method for system copy is only supported for offline

backups (which we don't have!):

N O T E

The system copy procedure does not support the usage of an online backup to copy your

Java engine.

[symon_braunbaer · Accepted solution]

So I guess I'll need to negotiate a maint. window for export of the source system... Thank you!!

[Reagan · Accepted solution]

Hello Symon

Thanks. Just for your information there is an option called "Assumed Answered" as well. This doesn't necessarily award any points to the contributors of a thread. You can also mark helpful answers if a reply was helpful but for the goodwill of the community it is better to mark the answer which was the real solution.

I have used online database backups for J2EE system copies. The reason (what I can think of) why SAP suggests to use an offline backup is to have a consistent target system after the system copy.

The solution suggested by Ashutosh is also a valid one.

If you are using an Oracle online backup then you will need to recover the database.

Regards

RB

[former_member185239]

Hi Symon,

1. Is your database has been restore ?

2. Is your database is running ?

If your answer is YES for both the question. then

create a CONTROL.SQL file in the sapinst directory (Everything in capital)

open the CONTROL.SQL and type exit;

Now input the same file in SAPINST.

It will read the CONTROL.SQL file and come out from it after reading the exit.

With Regards

Ashutosh Chaturvedi

[former_member188883]

Hi Symon,

Note: As a part of backup/ restore process we create a new control.sql file using the command

SQL> alter database backup controlfile to trace;

Rename this trace file to control.sql and place it in target system.

Please check the installation log folder for file CONTROL.SQL SAP installer checks for this file in installation log folder.

IF the database is up and running in target system & If file does not exist, you may create a new file with name CONTROL.SQL and add EXIT; line into it and save it.

Post this installation should proceed.

Hope this helps.

Regards,

Deepak Kori