on 04-03-2009 5:50 PM
Hi guys,
we are getting the strangest thing up here.
We did an upgrade from 46B to ECC6, which was succesful.
At this moment we want to do the unicode conversion and here is where the fun-part begins.
The prerequisites done via sapinst are OK
tablesplitting not necessary.
Database export via SAPinst ends after 5 sec (for a database of 300 GB) with the message: Succesful!
But NO export files were created.
Anyone an idea about this?
We are using the latest R3load, sapinst etc
Tried it with the non-unicode and unicode sapinst, both with the same result.
No errors were found in the logfile (offcourse not, everything went fine according the sapinst).
I already searched the notes, sdn and the internet but no solution found.
system is AIX, db = oracle 10
cheers,
Johnny
Hello,
I know at least one case in which this happens (it happened to me):
If the database server has a virtual hostname and you omit the SAPINST_USE_HOSTNAME property in the call to SAPINST, then this is seemingly accepted (steps like "Export Preparation" actually work normally), but in reality nothing is done.
Solution: include SAPINST_USE_HOSTNAME=<virtual_dbhostname>
Please check this and let us know.
Regards,
Mark
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
>
> I know at least one case in which this happens (it happened to me):
> If the database server has a virtual hostname and you omit the SAPINST_USE_HOSTNAME property in the call to SAPINST, then this is seemingly accepted (steps like "Export Preparation" actually work normally), but in reality nothing is done.
> Solution: include SAPINST_USE_HOSTNAME=<virtual_dbhostname>
Hi Mark,
We're running a CI with no HA or virtual setup, but nevertheless the SAPINST_USE_HOSTNAME variable indeed did the trick.
We were running SAPinst on the server and instgui remotely which was different from our previous test migration, were we ran SAPinst on the server console.Therefore I have the impression that this issue is related in how we started SAPinst.
Regards,
(& hartelijk dank)
Ben Sansen / Johnny Ramaekers
I would suggest that the sapinst is using the same temporary directory as during an installation/previous export.
I would do
mkdir /<somedirectory>
cd /<somedirectory>
<mountpoint>/<full-path-to-sapinst>
instead of cd'ing to the installation directory and calling sapinst using "./sapinst".
Markus
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Johnny,
> The prerequisites done via sapinst are OK
But have you also done the preparation steps in the ABAP system before you try to unload the database?
For example sapnote #932779 describes the nametabs that are used by the unicode conversion .. just a quote:
2.1 The nametab switch
1) You are in a Non Unicode System. All Unicode preparation steps
have been accomplished. So you have the nametab tables:
.....
Nametabs filled by RADCUCNT
......
2) Now you do the Unicode export of the database with R3load. The
nametabs are exported with the package SAPSDIC or SAPNTAB
depending on basis release. During the export, several files
are created by R3load which contain meta information about
package contents.
I guess that you have forgotten the unicode preparation steps before the export.
The report RADCUCNT is just one step in the preparation.. the whole unicode preparation depends on your type of system (Single codepage / MDMP / Combined Upgrade, etc..) .. check sapnote #548016 for that.
Regards
Stefan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
80 | |
24 | |
11 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.