Portal export/import on database 8.1.7 on an other machine

Hello,
I'm running Oracle8i on AIX. I have problem when I try full export/import my database (version 8.1.7) on an other machine. I have a problem with import users PORTAL30 and PORTAL30_SSO and CREATE TABLE 'WWSEC_ENABLER_CONFIG_INFO$'
The log when import full is:
IMP-00017: following statement failed with ORACLE error 22973:
"CREATE TABLE "WWSEC_ENABLER_CONFIG_INFO$" OF "SEC_ENABLER_CONFIG_TYPE" OID "
"'BA6473B86EF248BEE0330A18780F48BE' ( PRIMARY KEY ("LS_LOGIN_URL")) OBJECT "
"ID PRIMARY KEY PCTFREE 10 PCTUSED 40 INITRANS 1 MAXTRANS 255 LOGGING STORAG"
"E(INITIAL 131072 NEXT 131072 MINEXTENTS 1 MAXEXTENTS 4096 PCTINCREASE 0 FRE"
"ELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT) TABLESPACE "TBS_PORTAL""
IMP-00003: ORACLE error 22973 encountered
ORA-22973: size of object identifier exceeds maximum size allowed
Thank you.
Borjana Zekic

When using export/import between different releases, you need to use the older version of export to create your dump file. In your case, you must use the 8.0.5 export utility to export from your 8.1.7 database. You need a tnsname in your 8.0.5 tnsnames.ora that points to your 8.1.7 database. Then you use SQL Net to connect and do the export. So, instead of doing exp system/manager you would do exp system/manager@tnsname. Just be sure to use the 8.0.5 export, and your import will work fine.

Similar Messages

Portal Export Import with DB on different OS

Hi All,
I have a quick question about exporting the OracleAS Portal Metadata Repository database. Our source DB is on a different OS to our target DB.
We are going to apply the 10.1.2.3 patch and associated portal export/import patches to both nodes (from note 263995.1).
Our understanding was that we would use the method described in Chapter 10 of the Portal 10.1.4 Admin Guide (http://download.oracle.com/docs/cd/B14099_18/portal.1014/b19305/cg_imex.htm).
However, according to metalink note#276620.1, because our source and target OS are different, we should use the database export/import methodology that is described in Chapter 11 of the Application Server 10.1.2 Admin Guide (http://download.oracle.com/docs/cd/B14099_18/core.1012/b13995/prodtest.htm).
Could anyone tell me which way is better, we would prefer to use the database export/import method, has anyone tried this and what are their experiences.
Regards,
Tim.

kirwantd wrote:
We are going to apply the 10.1.2.3 patch and associated portal export/import patches to both nodes (from note 263995.1).
Our understanding was that we would use the method described in Chapter 10 of the Portal 10.1.4 Admin Guide (http://download.oracle.com/docs/cd/B14099_18/portal.1014/b19305/cg_imex.htm).
However, according to metalink note #276620.1, because our source and target OS are different, we should use the database export/import methodology that is described in Chapter 11 of the Application Server 10.1.2 Admin Guide (http://download.oracle.com/docs/cd/B14099_18/core.1012/b13995/prodtest.htm).
Could anyone tell me which way is better, we would prefer to use the database export/import method, has anyone tried this and what are their experiences.
Regards,
Tim.As far as your referred Metalink note is concerned, it gives you three options to move your repository with if you are working with 10.1.4 Portal.
It's a difference of can, should and must.
- It only shows ability to use three options ( can );
- on the whole, it does not give preferences for any method ( should );
- nor does it put a requirement for any single option ( must ).
( the only requirement/prohibition is for the option 2 which is not supported ).
we have used the first three methods given on the note (yes, we also tried 2; this note came later). 1 is what we use regularly for transports between environments; and 3 we use for environment staging (as given in chap 11 of pt. 3). both can be messy with a large repository (we do so for about ~400 GB) repository. but following that supportability guide (Metalink Note 333867.1), method 1 works too.
hope that helps!
AMN

Backout plan for Portal Export/Import

What is the best backout plan while doing the PORTAL export/import? Is cold backup of the Portal instance a good idea?

Dear Tarique,
I believe what you are looking is something like:-
ldapsearch -h %OIDHOST% -p %OIDPORT% -D cn=orcladmin -w %IAS_PASSWORD% -b "cn=IAS Infrastructure Databases,cn=IAS,cn=Products,cn=OracleContext" -s sub "orclResourceName=portal" orclpasswordattribute
... substitute the %OIDHOST% , %OIDPORT% and %IAS_PASSWORD% for your values.
This should easely return your Portal schema password.
I hope it helps...
Cheers,
Pedro.

Portal export/import between 9.0.2 and 9.o.3

I am aware that you can not export/import between portal installations on different versions e.g. 3.0.9 and 9.0.2 but is it possible to do export/import between 9.0.2 and 9.0.3?

The FAQ only states:
<<<<Snip>>>>
Portal Export/Import utilities will only work between portal installations that are at the same revision level. For example, Portal Import/Export will copy content successfully between two 9.0.2.x instances of Portal, but not between a 9.0.2 portal instance and a 3.0.9 portal instance.
That said, Portal Export/Import WILL work between two portal instances that are of different "minor" revision levels. For example, Portal Export/Import will work between a 9.0.2.2.14 portal instance to a 9.0.2.2.22 portal instance, and vice versa.
<<<</Snip>>>>

Export/Import of Database to increase the number of datafiles

My BW system is close to 400 GB and it only has 3 datafiles. Since we have 8 CPU cores, I need 8 datafiles. What is the best way to export/import the database in order to achive 8 datafiles?

With a BW system that size you can probably get away with it. You most likely do at least a few full loads so all that data will be evenly distrubuted when you drop and reload. If you can clean up some of your PSAs and log tables you can probably shrink the 3 files down a little anyway. If you do little maintenance like that every few weeks, after locking auto growth, you can probably shave 2-3 GBs off each file each week. Do that for a few months and your large files will love 20 GBs while the other ones start to grow. Rebuilding indexes also helps with that. You will be surprised how fast they will level out that way.
With regard to performance you should be fine. I certainly wouldnt do it at 10 am on Tuesday though :-). You can probably get away with it over a weekend though. It will take basically no time at all to create them and very little IO. If you choose to clean out the 3 existing ones that will take some time. I have found it takes about 1-3 hours to shrink a 150 GB datafile down to 100 GBs, that was with 8 CPUs, 30 GBs of RAM, and an SAN that I don't fully understand

Issues with Export/Import using Database & Shared buffer

Hi All,
I have a method that calls a program via a job and I am having issues passing data between the two.
Note that two different users process the method and program (via job) resp. This is how I am calling the second prog-
SUBMIT ZPROGRAM
             VIA JOB     l_jobname
                 NUMBER l_jobcount
                 USER    i_user
             AND RETURN.
I need to pass data from method to the second program and vice versa and then the method continues its processing with the data acquired from the second program.
I have tried using Import/Export using database and also shared buffer. What I have found is that most of the times I am able to pass data from method to program. However the job takes a couple of min to execute and I think that the data is not making back to the method in time.
I have looked at some useful forum links-
Problem with export/import in back ground
Re: EXPORT/IMPORT to MEMORY
but havent been able to find an answer yet. Any solution? Thanks in advance for your help!
Liz

Hi Suhas, Subhankar
I have tested the scenario without the job previously itself and it works. Thats the reason, i am trying with the job now as my requirement is that I need to change the user while executing the second report.
Here is an example of my import/export - I am passing the return value from the second report to the first.
Code in second report-
DATA: INDXKEY LIKE INDX-SRTFD VALUE 'RET1'.
INDX-AEDAT = SY-DATUM.
INDX-USERA = SY-UNAME.
EXPORT RETURN1 TO SHARED BUFFER INDX(ST) ID INDXKEY.
Code in first report -
SUBMIT ZPROGRAM
                 VIA JOB     l_jobname
                     NUMBER l_jobcount
                     USER    i_user
                 AND RETURN.
Once Job close FM is executed successfully, I import the values as follows
IMPORT RETURN1 TO RETURN1 FROM SHARED BUFFER INDX(ST) ID INDXKEY3.
INDXKEY is having value RET1.
However Return1 is not having any values in first report. It has some value in executed without the job
Please note that I have tried Export/import with Database too and I am getting the same results.
Thanks for your suggestions.
Regards, Liz

Portal export & import

hi all,
can anyone please post here the detail steps of export & import of portal information of the same release on same server (ie, 10.1.2.0.2).
Thanks.

Here:
http://download.oracle.com/docs/cd/B14099_19/portal.1012/b14037/cg_imex.htm#i1030999

Portal Export / Import Problems

I'm trying to export a Portal application from a solaris development machine running Portal 3.0.7 to a solaris production machine running 3.0.8 and I'm having problems.
As a starter I thought I'd try just the Login Server and the Security bits in that order.
Everything seems to go okay with both the export and import using ssoexp.csh/ssoimp.csh and secexp.csh/secimp.csh but when I navigate to the new production site and try to login with one of the usernames and passwords that should have been imported, I get an authentication failure.
Any ideas ?
Thanks
Garry

Folks,
Here is the output I receive after running the appropriate import scripts
Import of Login Server
Initializing Merge ...
Initialization Complete
Activity Log:
Merging import SSO data with existing data
The user PORTAL30_SSO with Login Server role FULL Exists ...
... The imported user has Login Server role = FULL
The user PORTAL30_SSO_ADMIN with Login Server role FULL Exists ...
... The imported user has Login Server role = FULL
The user PUBLIC with Login Server role USER Exists ...
... The imported user has Login Server role = USER
The user PORTAL30 with Login Server role FULL Exists ...
... The imported user has Login Server role = FULL
The user PORTAL30_ADMIN with Login Server role FULL Exists ...
... The imported user has Login Server role = FULL
Disconnected from Oracle8i Enterprise Edition Release 8.1.7.0.0 - Production
With the Partitioning option
JServer Release 8.1.7.0.0 - Production
Import of Login Server User Information Complete
Note: A imported user has to login to the Login Server with
password the same as his/her user name and reset his/her password.
Import of Security data
Initializing Merge ...
Initialization Complete
Activity Log:
Merging imported security data of Portal with existing data
The user PORTAL30 exists with ID: 0
The user PORTAL30_ADMIN exists with ID: 1
The user PUBLIC exists with ID: 2
The user PORTAL30_SSO exists with ID: 3
The group AUTHENTICATED_USERS exists with ID: 0
The group DBA exists with ID: 1
The group PORTAL_ADMINISTRATORS exists with ID: 2
The group PORTLET_PUBLISHERS exists with ID: 3
The group PORTAL_DEVELOPERS exists with ID: 4
Disconnected from Oracle8i Enterprise Edition Release 8.1.7.0.0 - Production
With the Partitioning option
JServer Release 8.1.7.0.0 - Production
Import of Security Data Complete
From the output you can see that there is data being imported for the Portal users but not OPDSTATS the user I wish to use, and have created on my development site.
However the WWUTL_SSO_TX_PERSON$ table has an entry created for OPDSTATS. I have compared the encrypted passwords for opdstats on dev and prod databases and they are the same.
The logon user OPDSTATS uses a schema called OPDUSER that is not created on the database after import of both Login Server and Security.
I can however logon as portal30 and have tried updating the table WWUTL_SSO_TX_PERSON$ with the portal30 encrypted password for the opdstats user, again this was unsuccessful.
Any idea anyone ?
Thanks
Garry
null

Export/Import full database dump fails to recreate the workspaces

Hi,
We are studying the possibility of using Oracle Workspace to maintain multiple versions of our business data. I recently did some tests with the import/export of a dump that contains multiple workspaces. I'm not able to import the dump successfully because it doesn't recreate the workspaces on the target database instance, which is an empty Oracle database freshly created. Before to launch the import with the Oracle Data Pump utility, I have the "LIVE" workspace that exists in the WMSYS.WM$WORKSPACES_TABLE table. After the import is done, there is nothing in that table...
The versions of the Oracle database and Oracle Workspace Manager are the same on source and target database:
Database version (from the V$VERSION view):
Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bi
PL/SQL Release 10.2.0.4.0 - Production
CORE 10.2.0.4.0 Production
TNS for 64-bit Windows: Version 10.2.0.4.0 - Production
NLSRTL Version 10.2.0.4.0 - Production
Workspace Manager version (from the WM_INSTALLATION view):
OWM_VERSION: 10.2.0.4.3
In order to recreate the tablespaces successfully during the full import of the dump, the directory structure for the tablespaces is the same on the target database's computer. I used the instructions given in this document, section "1.6 Import and Export Considerations" at page 1-19:
http://www.wyswert.com/documentation/oracle/database/11.2/appdev.112/e11826.pdf
Considering that the release of Oracle database used is version 10.2.0.4, I use the following command to import the dump since it doesn't contain the WMSYS schema:
impdp system/<password>@<database> DIRECTORY=data_pump_dir DUMPFILE=expfull.dmp FULL=y TABLE_EXISTS_ACTION=append LOGFILE=impfull.log
The only hints I have in the import log file are the following block of lines:
1st one:
==============================
Traitement du type d'objet DATABASE_EXPORT/SYSTEM_PROCOBJACT/PRE_SYSTEM_ACTIONS/PROCACT_SYSTEM
ORA-39083: Echec de la création du type d'objet PROCACT_SYSTEM avec erreur :
ORA-01843: ce n'est pas un mois valide
SQL en échec :
BEGIN
if (system.wm$_check_install) then
return ;
end if ;
begin execute immediate 'insert into wmsys.wm$workspaces_table
values(''LIVE'',
''194'',
''-1'',
2nd one at the end of the import process:
==============================
Traitement du type d'objet DATABASE_EXPORT/SCHEMA/POST_SCHEMA/PROCACT_SCHEMA
ORA-39083: Echec de la création du type d'objet PROCACT_SCHEMA avec erreur :
ORA-20000: Workspace Manager Not Properly Installed
SQL en échec :
BEGIN
declare
compile_exception EXCEPTION;
PRAGMA EXCEPTION_INIT(compile_exception, -24344);
begin
if (system.wm$_check_install) then
return ;
end if ;
execute immediate 'alter package wmsys.ltadm compile';
execute immediate 'alter packag
The target operating system is in french... here is a raw translation:
1st one:
==============================
Treatment of object type DATABASE_EXPORT/SYSTEM_PROCOBJACT/PRE_SYSTEM_ACTIONS/PROCACT_SYSTEM
ORA-39083: Object type creation failed PROCACT_SYSTEM with error :
ORA-01843: invalid month
failed SQL :
BEGIN
if (system.wm$_check_install) then
return ;
end if ;
begin execute immediate 'insert into wmsys.wm$workspaces_table
values(''LIVE'',
''194'',
''-1'',
2nd one at the end of the import process:
==============================
Treatment of object type DATABASE_EXPORT/SCHEMA/POST_SCHEMA/PROCACT_SCHEMA
ORA-39083: Object type creation failed PROCACT_SCHEMA with error :
ORA-20000: Workspace Manager Not Properly Installed
failed SQL :
BEGIN
declare
compile_exception EXCEPTION;
PRAGMA EXCEPTION_INIT(compile_exception, -24344);
begin
if (system.wm$_check_install) then
return ;
end if ;
execute immediate 'alter package wmsys.ltadm compile';
execute immediate 'alter packag
By the way, the computer of the source database is Vista 64 in english and the destination computer is Vista 64 in french, do you think this has anything to do with these error messages? The parameters of the NLS_SESSION_PARAMETERS view are the same in the source and target database...
Thanks in advance for your help!
Joel Autotte
Lead Developer
Edited by: 871007 on Jul 13, 2011 7:31 AM

I tried to import the full database dump with the "imp" command and I had the same error message with more detail:
. Import d'objets SYSTEM dans SYSTEM
IMP-00017: Echec de l'instruction suivante avec erreur ORACLE 1843 :
"BEGIN "
"if (system.wm$_check_install) then"
" return ;"
" end if ;"
" begin execute immediate 'insert into wmsys.wm$workspaces_ta"
"ble"
" values(''LIVE'',"
" ''194'',"
" ''-1'',"
" ''SYS'',"
" *to_date(''09-DEC-2009 00:00:00'', ''DD-MON-YYYY HH"*
*"24:MI:SS''),"*
" ''0'',"
" ''UNLOCKED'',"
" ''0'',"
" ''0'',"
" ''37'',"
" ''CRS_ALLNONCR'',"
" to_date(''06-APR-2011 14:24:57'', ''DD-MON-YYYY HH"
"24:MI:SS''),"
" ''0'',"
" '''')'; end;"
"COMMIT; END;"
IMP-00003: Erreur ORACLE 1843 rencontrée
ORA-01843: ce n'est pas un mois valide
ORA-06512: à ligne 5
The call to the TO_DATE function with the string of the date format is incompatible with the format and language set in the NLS parameters of my database. Since I know that the "imp" and "exp" commands work client side (unlike "impdp" and "expdp"), I did a full export of the source database from the computer on which I try to import the dump to have the same language exported in the dump and I was able to import the dump successfully.
But, I would like to use the Data Pump tool instead of the old import and export tools. How would it be possible to set the NLS parameters that "impdp" must use before to launch the import of the dump?
The NLS parameters are set to the "AMERICAN" settings in both source and destination database when I validate that with the "NLS_DATABASE_PARAMETERS" view. The dump I did with "expdp" on the source database exported the data with the "AMERICAN" settings as well...
On the destination database, the computer language is in french and I guess it is considered by the Data Pump import tool since it outputs the log in the language of the computer and it tries to do a TO_DATE with the wrong date format because it works with the "CANADIAN FRENCH" settings...
Any suggestions? I'll continue to read on my side and re-post if I find the solution.
Thanks!
Edited by: 871007 on Jul 19, 2011 8:42 AM
Edited by: 871007 on Jul 19, 2011 8:43 AM
Edited by: 871007 on Jul 19, 2011 8:43 AM

Export-import if database is down

I had a query whether we can run the export and the import process if the database is down. Basically export process is the command, 'exp'. So, would this
command run even if the database is down. Even, import command is run with command, 'imp', so, would it be requiring database to be up.
I hope, my question is clear.
Please, help in solving the doubt.
regards

Hi,
Export is a Logical Backup in sense DB Objects, Think how come with out DB instance is Up and Running, does exp application can extract the things.
- Pavan Kumar N

Exports / Imports on Databases with VPD

I'm running Oracle 11.1.0.7, with VPD. I'm trying to use datapump to export and import the data from one machine to another.
Not all the information in all the tables is making it across. Is there a special role or privilege that will allow SYSTEM (as opposed to SYS as SYSDBA) to grab all the data?

I'm running Oracle 11.1.0.7, with VPD. I'm trying to use datapump to export and import the data from one machine to another.
Not all the information in all the tables is making it across. Is there a special role or privilege that will allow SYSTEM (as opposed to SYS as SYSDBA) to grab all the data?

EXPORT/IMPORT DB PROVIDER NT-- SOLARIS IN PORTAL RELEASE 2

Hi,
I've been assigned to export/import a database provider with all the applications contained therein from NT platform to SUN SOLARIS platform. Can anyone please kindly tell how to do this or where to get the step-by-step guide for this task.
Thanks.

hi,
i am using portal 9.0.4 in windows 2003 server. i am searching for the step-by-step import/export details. you told you have got it. can you share with me the same?
my email id is [email protected] i am in-search of export/import commands. i am able to export through the transport set, but the import will show the importing details, but nothing is available. please help me.
regards
sudhir

Portal Export and Import Steps

Hi all,
I need to export all page groups from Production portal instance and import those in brand new portal instance (target Portal)*. Source and target portal instance is as follows
Production Oracle Database Version: 10.1.0.5
Target Oracle Database Version: 10.2.0.4
Production Oracle Infrastructure Version : 10.1.2.0.2
Target Oracle Infrastructure Version: 10.1.2.0.2
Production Portal Version: 10.1.2.0.2
Target Portal Version: 10.1.2.0.2
What i have done till now is as follows
1. Install Database server 10.2.0.1
2. Upgrade Database Server to 10.2.0.4
3. Install 10.2.0.1 products from Companion CD (ultra search Schemas)
4. Create Metadata Repository using Repository Creation assistance
5. Install IAS infrastructure (10.1.2.0.2)
6. Install IAS Middle Tier (10.1.2.02.)
7. Create Transport sets in production instance
Please tell me what i am supposed to do now.
I am following below link for reference but not able to follow all
http://www.scott-tiger.dk/portalHelp2/ohw/state?navSetId=_&navId=0
Regards
Anindya

For Portal Export Import (transport), the following are the foremost links on Metalink/ My Oracle Support.
Note 306785.1 Overview of the Portal Export-Import Process
Note 263995.1 - Master Note for OracleAS Portal Export / Import Issues
Note 333867.1 Portal Export and Import Utility Supportability Scenarios
Regarding your question, please do go through all of these notes.
- Overview will tell you how to prepare your instances/environments for portal transport. you will see how to ensure they are ready, and that some patches are needed.
- Master note will tell you which patches are needed, how to get them, what are the diagnostic tools which can help you check and clean your portal repositories, and what common errors you may get and how to fix them.
- Supportability Scenario tells you what actually you can transport and what you cannot. i.e., what is supported and what is not. Do read it for your case.
I have seen several Portal Admins who keep banging their heads with problems they create in their systems because they do not read this note and try to force a case which does not follow a supportable scenario.
hope that helps!
AMN

Export/Import scripts not working

We're trying to move a portal from one server to another server (different hardware). We haven't been able to successfully complete this process--are there any updated scripts out there from Oracle that make this possible?

2 questions
1. Have you tried using the Portal export/import utilities ?
2. Have you installed Portal and Login server in the target database before attempting 1 above ?
3. Have you patched the Portal repository to the same patch level as that of the source database Portal Repository?

Moving entire portal instance to new database

Does anyone have scripts for exporting/importing an entire portal instance? I'm moving my development database from Windows NT to a Sun box, and since I can't move the database directly I need to do a full portal export/import of all portal contents (pages, applications, content areas, etc.).
Thanks in advance.
Cecil...

Hi Cecil,
I have found the portal export/import routines to be a bit buggy. Try it with care. In moving from NT to Sun I have trusted the full database export/import and it worked out just fine.
On the Sun database just drop all the portal users (including portal30, portal30_sso, etc.). Then do a full database import on the Sun from the NT export. An important final note is to run the "ssodatan.sh" script to point to your new server.
Hope this helps.
Bob Bob,
Would you consider talking with me about this? I have a couple questions, like, if I'm moving to a new database then I won't have a PORTAL30 or PORTAL30_SSO to drop befoe the import, or do I install Portal into the new DB, then drop the users, then impoer, etc. If you can discuss this, please send contact info to [email protected]
Thanks!
Cecil...

Portal export/import on database 8.1.7 on an other machine

Similar Messages

Maybe you are looking for