on 03-15-2013 1:32 PM
Dear all,
I'm preparing for OS migration, systtem copy of the source system (HP-UX 11.31, Oracle 11.2.0.3) and target system (RedHat 6, Oracle 11.2.0.3), ECC6.0 ABAP only Central system installation.
In the documentation I've found the R3LOAD constratints for:
R3load only: Indexes longer than 18 characters are not allowed on the database to be exported.
I've checked:
select index_name from dba_indexes where length(index_name)> 18;
------
2585 rows selected.
Should I rename the indexes before the export and then after the import on the target to rename to the names before?
Or the SAPinst have some step that includes this problem?
Thank you in advance.
BR,
Ruzica
Hi,
Please use the latest SAPINST & Kernel version ...
Some of the bugs like this has been corrected in the latest kernel version..
Kindly use those kernels.
Thanks and Regards,
Vimal
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks Vimal,
I've downloaded the latest kernels I hope this will help.
BR,
Ruzica
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes Joe,
I think you're right:
-----
SYS_IL0000381735C00002$$
SYS_IL0000381730C00006$$
SYS_IL0000381705C00002$$
SYS_IL0000381705C00003$$
SYS_IL0000381705C00004$$
SYS_IL0000381682C00005$$
SYS_IL0000381669C00005$$
SYS_IL0000381630C00006$$
SYS_IL0000381611C00006$$
SYS_IL0000381559C00005$$
SYS_IL0000381559C00006$$
MGMT_TYPE_PROPERTIES_PK
MGMT_TYPE_PROPERTIES_IDX_01
MGMT_TARGETS_IDX_01
MGMT_TARGETS_IDX_02
MGMT_TARGET_TYPES_PK
MGMT_METRICS_EXT_PK
MGMT_METRICS_IDX_01
MGMT_METRICS_IDX_03
MGMT_TARGET_BASELINES_DATA_PK
MGMT_TARGET_BASELINES_PK
MGMT_MASTER_CHANGED_CBACK_PK
PK_MGMT_MASTER_AGENT
MGMT_AVAIL_MARKER_PK
CUR_AVAIL_PRIMARY_KEY
AVAILABILITY_PRIMARY_KEY
MGMT_REBUILD_INDEXES_PK
INDEX_SIZES_PRIMARY_KEY
TABLE_SIZES_PRIMARY_KEY
----
and others ...
These are the Lobindexes from the Oracle dictionary.
Because I've already install the Oracle on the target, these indexes should be here.
BR,
Ruzica
Well, those beginning with SYS_IL look pretty much like lobindexes.
Others like MGMT_TYPE_PROPERTIES_PK probably aren't.
But I think they aren't SAP indexes anyway.
To make sure, I would try this:
select index_name, index_type, owner
from dba_indexes
where length(index_name)> 18;
You may exclude all entries where owner isn't SAP schema user (sapsr3 or whatever) or where type is LOB.
regards
Hi Joe,
Some are LOB some Normal. But I'm still confused , should I not wory about these indexes in the SAPinst with R3LOAD export and import ?
INDEX_NAME INDEX_TYPE
------------------------------ ---------------------------
OWNER
------------------------------
WRI$_SQLSET_DEFINITIONS_IDX_01 NORMAL
SYS
WRI$_ADV_SQLT_RTN_PLAN_PK NORMAL
SYS
SYS_IL0000271649C00040$$ LOB
SYS
WRI$_ADV_SQLT_PLANS_PK NORMAL
SYS
WRI$_ADV_SQLT_STATISTICS_PK NORMAL
SYS
SYS_IL0000271643C00004$$ LOB
SYS
.......
2585 rows selected.
tnx,
Ruzica
No,
R3load will not touch the objects owned by SYS.
Those objects are created during installation of the target system. So they will already be there, when R3load starts importing SAP objects.
And LOB segments owned by SAPSR3 (not sure if they exist in your system, they do exist in our systems) will implicitly be handled by Oracle, when the corresponding SAP table is created.
So, depending on whether or not SAPSR3 owns lobindexes in your system, I maybe shouldnt have mentioned them at all.
It might have been sufficient to tell you that R3load doesn't touch non-SAP objects.
regards
User | Count |
---|---|
91 | |
10 | |
10 | |
9 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.