DAC Repository upgrade

Hi ,
Im trying to upgrade DAC repository,we are doing a BI APPS upgrade from 7.9.6 to 7.9.6.3.
We are only just upgrading the DAC repository ,we are not changing the Version of DAC.
How can we do this,any step are really appreciated.
Regards,
KK

You will be using DAC client -->Tools-->DAC Repository Management--> Upgrade or Merge wizard to do so..
Check in the Chapter no 10 of DAC user guide..
Mark helpfull if it helps..
Regards,
Veeresh Rayan

Similar Messages

DAC 10.1.3.4.1 First Time Login Repository Upgrade Failure

Hi all,
We are upgrading from DAC shipped with Siebel Analytics Applications 7.8.4 to DAC 10.1.3.4.1, platform and repository. This is combined with OBIEE upgrade from Analytics 7.8.5.2 to OBIEE 11g (11.1.1.5.0) and OBIA upgrade from Analytics Applications 7.8.4 to OBIA 7.9.6.3. Additionally, the database was upgraded from Oracle 10.2.0.2 to 11.2.0.2.
We've just installed DAC 10.1.3.4.1 on a Windows 2008 (32bit) Server and this completed without issue. When logging in to the DAC Client and making a connection to the existing DAC Repository, after 'Yes' when prompted to upgrade the existing repository, we get a message saying, ["Upgrade didn't complete! Please check log file "log/upgrade.txt" for details."] Upon checking the log file, it states the following:
###start of message###
=======================================
Upgrade from DAC 1.0 to Dactopus format
=======================================
reading upgrade stage...
nothing found - starting upgrade
No upgrade from DAC 1.0 to Dactopus is currently available.
If you want to have a Dactopus repository at the current connection,
you should first drop existing one using 7.8.2.4 DAC build.
upgrade failed
###end of message###
Please, can someone shed some light on the situation?
Many thanks.
PS. We were able to create a new Oracle user, create a new DAC Repository on this new schema and import the OBIA 7.9.6.3 DAC Repository without apparent issue.

Hello all,
I have a conclusion to this question.
Whilst Oracle Support did not explain the error message per se, they did state that one cannot upgrade a DAC 7.8.4 Repository via the First Time Login prompt, but rather to use the Upgrade/Merge Wizard, option 'Repository Upgrade (DAC 784)'. if the customisations are substantial. If the customisations are simple, they can be done manually - see upgrade guides.
Whilst this is indeed stated in the upgrade documentation, I had been confused by other statements in the documents which appeared to be contradictory and ultimately lead me down the wrong upgrade path.
Just do add, the documentation recommends using the Upgrade/Merge Wizard 'Repository Upgrade (DAC 784)' option if the customisations are substantial and unknown. If the customisations are simple and known, they can be done manually - see upgrade guides.
Thanks.

Repository upgrade fails 11.1.0.7 db -10.2.0.5 GC patchset

Installing GridControl 10.2.0.5 on Windows 2003 Server SP2. Initial install successful of 10.2.0.2 using existing database 11.1.0.7. The database was created new to use for GC. Patchset no problems until Configuration Assitant step "Repository Upgrade" failed with errors:
rem Copyright (c) 1999, 2009, Oracle. All rights reserved.
oracle.sysman.emcp.oms.RepositoryPatchUpgrade -verbose
oracle.sysman.emcp.oms.OmsPatchUpgrade -configureOms
oracle.sysman.emcp.aggregates.ConfigPlugIn
oracle.sysman.emcp.oms.StartOMS -configureOms
oracle.sysman.emcp.oms.EMCLISetup
oracle.sysman.ccr.configCCR.ConfigCCRPlugIn
oracle.sysman.ccr.configCCR.ConfigRepeaterPlugIn
Tried to find cause of errors and cannot seem to understand why this step failed.
Considering uninstalling GC and Oracle 11g and reinstalling GC with "new database" option.
Anyone successful at installing GC 10.2.0.5 with an 11g database?
Thank you,
Curt Swartzlander
DBA

pasinc wrote:
Can anyone help me figure out why the domU is just hanging/blocked?It's not hanging (blocked just means it doesn't need the CPU) -- it's just switched into a graphic mode that the console view can't display. You can either VNC into the guest, or change the kernel boot parameters by removing rhgb quiet and replacing them with console=xvc0 -- this should allow you to see the full boot process and answer the first-boot interview questions without using VNC.
You can get the VNC details by running: virsh dumpxml <domain ID> and you can get the domain ID from the xm list output.

Error while Importing Metadata into DAC Repository

Hi,
After the successful first time login into DAC and creating repository, when I try to import metadata into DAC repository.
DAC > Tools > DAC Repository Management > Import
I don't see any Applications listed under "Application List"
Can anybody suggest the troubleshooting steps for this?
Regards,
Jitendra

If this is the first time that you are importing make sure that the directory you are importing from is like this -
C:\OBIEE\OracleBI\DAC\export
If this is not the first time then
Can you go inside the following directory
C:\OBIEE\OracleBI\DAC\log
and check for export.log - Look for Applications Section, if you have any application then you had exported it and you should see it under the applications tab when importing otherwise you don't !!Since its an xml file that is generated i believe you have not exported by selecting the applications yo want and that is your problem.
Hope this helps !!
Cheers,
Sid

9.0.2.6 Portal Repository Upgrade Patch problems.

We got some problem with Portal when tryed to apply
9.0.2.6 Upgrade. Could anybody give advice on this issue:
Initial configuration:
Solaris8, Portal 9.0.2.2.14, Oracle 9iAS R2 v.9.0.2.0, RDBMS 9.0.1.3. The infrastructure and midtier work on different SPARC-servers.
Accordingly upgrade procedure we succesfully applied:
a) Infrastructure: 9.0.1.4 Patchset for Oracle RDBMS server, 9.0.2.2 Patchset for OID, Oracle 9iAS SSO-server
migration to 9.0.2.5, 9.0.2.2 Patchset for 9iAS Core.
b) 9.0.1.4 Patchset for Oracle RDBMS server, 9.0.2.2 Patchset for OID, Oracle 9iAS SSO-server migration to 9.0.2.5, 9.0.2.2 Patchset for 9iAS Core, Portal 9.0.2.6
patch.
After this we needed to make just one last step:
Portal 9.0.2.6 Repository Upgrade Patch (2981297) for
changing Portal's repository schemes. It worked but
like a result we got the next errors after patch upgrade
was done:
a) "The following invalid non-Portal objects exist in the Portal Schema: INDEX ABC (the name of portal object), PACKAGE BODY WWMON_REP_REPOSITORY, PACKAGE BODY WWMON_REP_REPOSIT_DTL, PLS-00103: Encountered the symbol "," when expecting one of the following: (-+case mod not null <an identifier>,...) The symbol "null" was substituted for "," to continue.)" See upgtmp/nonportal.log
b) "ERROR: 1 invalid objects remain; ERROR: Failed while updating the new portlet IDS..."
c) "ERROR: ORA-01407: cannot update ("PORTAL"."WWSBR_URL$"."URL") to NULL.
d) Two package body of packages at PORTAL scheme became invalid: WWMON_REP_REPOSITORY, WWMON_REP_REPOSIT_DTL. About 20 package body of packages at PORTAL_DEMO became invalid (It seems like initial portlet ID's disappeared
and except of pportlet_id there is nothing:
Example:
inital statement at body:
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
PORTAL.wwpro_api_invalidation.invalidate_cache(
p_provider_id => p_provider_id,
p_portletid => 1065753336,
p_instance_id => p_reference_path,
p_subscriber_id => PORTAL.wwctx_api.get_subscriber_id ,
p_user => PORTAL.wwctx_api.get_user);
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
after upgrade repository patch:
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
PORTAL.wwpro_api_invalidation.invalidate_cache(
p_provider_id => p_provider_id,
p_portletid => ,
p_instance_id => p_reference_path,
p_subscriber_id => PORTAL.wwctx_api.get_subscriber_id ,
p_user => PORTAL.wwctx_api.get_user);
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Like a result after 9.0.2.6 Portal Repository Upgrade Patch application we lost the possibility to edit user's
profiles at Portal and other nesessary features. It seems
like some portlet ID's just dissapeared from Portal scheme. Could anybody had the same problem with Portal Upgrade 9.0.2.6? Quite possible that we missed some important element at during upgrade but ,really, we didn't wait so unlucky result. Advice something, please...
Regards. Igor.

Igor,
Since you've encountered undocumented errors, your repository upgrade has failed. You'll want to leave the repository as is for troublshooting, if at all possible, and log a TAR with support if you haven't already. They'll ask you to upload your upgrade log file and your upgrade tmp directory.
Regards

Portal repository upgrade problems

I upgraded a ORACLE 8.1.6.3.0 database to 8.1.7.2.0 and JVM but 9 classes remained invalid, removing and reinstalling jvm I lost all Portal30 JAVA stuffs. Who has found a clue to make it correct.

Igor,
Since you've encountered undocumented errors, your repository upgrade has failed. You'll want to leave the repository as is for troublshooting, if at all possible, and log a TAR with support if you haven't already. They'll ask you to upload your upgrade log file and your upgrade tmp directory.
Regards

Warning on Exporting DAC Repository Metadata

After finishing export DAC repository metadata, we got some warning as following:
W_ETL_SA: 26 objects
31705 INFO Wed Nov 11 11:15:12 CST 2009 Exporting entity W_ETL_SA for application EBS 11.5.10.W
31706 INFO Wed Nov 11 11:15:12 CST 2009 Moved W_ETL_SA: 26 objects
31707 INFO Wed Nov 11 11:15:12 CST 2009 Exporting entity W_ETL_TABLE for application Universal
31708 WARNING Wed Nov 11 11:15:12 CST 2009 Mismatch between the number of records in the object reference table and objects
There are 14 warning of all.
Does it mean something wrong with DAC reposritory?
Roger

Hi,
I have spoken to Oracle about this previously, apparently these warnings are not important and are nothing to worry about, see here:
[http://obiee-tips.blogspot.com/2009/09/dac-importexport.html|http://obiee-tips.blogspot.com/2009/09/dac-importexport.html]
They still worry me a bit though...
Regards,
Matt

Errors running MRUA for Metadata Repository Upgrade to version 10.1.2.0.2

Hi,
I am encountering the following errors trying to run the MRUA for our Metadata Repository Upgrade on an AIX 5.3 box:
<mrua_runs> ../mrua/mrua.sh -oracle_home /u01/oracle/product/9.2.0.8 -oid_host ourhost.domain.com -oid_ssl_port 3130
Executing mrua.pl
Running on UNIX
OracleAS Metadata Repository Upgrade Assistant 10.1.4.0.1
Enter the password for SYS: <syspw>
Enter the password for cn=orcladmin: <pwd>
Exception in thread "main" java.lang.NoClassDefFoundError: oracle/sysman/oii/oiio/oiiol/OiiolTextLogger
at oracle.ias.repqueries.RepositoryQueries.formatGlobalDBName(RepositoryQueries.java:603)
at oracle.ias.mrua.RepQueries.getDBInfo(RepQueries.java:180)
at oracle.ias.mrua.Util.getTheDBInfo(Util.java:50)
at oracle.ias.mrua.MRUA.getInfoFromOID(MRUA.java:690)
at oracle.ias.mrua.MRUA.driver(MRUA.java:297)
at oracle.ias.mrua.MRUA.main(MRUA.java:193)
MRUA detected an error at /mnt/MRUA/mrua/mrua.pl line 237.
<mrua_runs>
Before running the MRUA for the Metadata Repository:
1. I have just recently completed a Middle Tier and Identity Mangement upgrade to 10.1.2.0.2 from version 9.0.4.1.
2. I was able to successfully run the MRUA upgrade script for upgrading our Portal Repository (customer database).
Our Metadata Repository database is at version 9.2.0.8. Has anyone seen these errors or had this problem?
The MRUA CD that I have is labelled "Oracle Metadata Repository Upgrade Assistant and Utilities 10g (10.1.2.0.2) for AIX based systems".
But in the errors I see "OracleAS Metadata Repository Upgrade Assistant 10.1.4.0.1". Is something wrong there? Should it say 10.1.2.0.2?
Any help would be greatly appreciated.
Thanks.
CV
Hi,
I have downloaded the 10.1.2.0.2 version of the MRUA and tried the upgrade again. This time I see the following errors:
Executing mrua.pl
Running on UNIX
OracleAS Metadata Repository Upgrade Assistant 10.1.2.0.2
Enter the password for SYS: <syspwd>
Enter the password for cn=orcladmin: <pwd>
Exception in thread "main" java.lang.NoClassDefFoundError: oracle/sysman/oii/oiio/oiiol/OiiolTextLogger
at oracle.ias.repqueries.RepositoryQueries.formatGlobalDBName(RepositoryQueries.java:603)
at oracle.ias.mrua.RepQueries.getDBInfo(RepQueries.java:180)
at oracle.ias.mrua.Util.getTheDBInfo(Util.java:50)
at oracle.ias.mrua.MRUA.getInfoFromOID(MRUA.java:784)
at oracle.ias.mrua.MRUA.driver(MRUA.java:290)
at oracle.ias.mrua.MRUA.main(MRUA.java:186)
MRUA detected an error at /mnt/MRUA_downloaded/ohome/mrua/mrua.pl line 239.
Thanks.
CV
Edited by: CV on Jul 28, 2009 1:37 PM

Hi,
Found out from Oracle that the "oracle/sysman/oii/oiio/oiiol/OiiolTextLogger" class is in the $ORACLE_HOME/oui/jlib/OraInstaller.jar file and as per their suggestion added the jar file to the $classpath list of jar files in the mrua.pl script. I tried running the MRUA again, and ran into the following errors:
Exception in thread "main" java.lang.NullPointerException
at oracle.ias.mrua.MRUA.formatHostPortSid(MRUA.java:1449)
at oracle.ias.mrua.MRUA.getInfoFromOID(MRUA.java:794)
at oracle.ias.mrua.MRUA.driver(MRUA.java:290)
at oracle.ias.mrua.MRUA.main(MRUA.java:186)
MRUA detected an error at /u01/oracle/mrua_runs/MRUA_downloaded/ohome/mrua/mrua.pl line 243.
I am still troubleshooting. So if you have any ideas please let me know.
Thanks.
CV

9.0.2 to 9.0.2.6 Upgrade - Repository Upgrade

Hi,
I am unable to do the Repository Upgrade for the 9026 Portal Upgrade. I have successfully done all the pre-requisite patchset upgrades as well as the actual 9026 Portal upgrade. But when I run the upgrade.pl, I get an error. Here are the steps:
Enter Schema Name: portal
Enter Schema Pwd: portal
Enter SYS Pwd: change_on_install
Enter TNS String: iasdb
### ERROR: Connection to Portal repository failed.
### DBI->Connect(iasdb) failed: ORA-01017: invalid username/password; log on denied (DBD ERROR: OCISessionBegin) at /u02/app/oracle/product/IAS20MT/portal/admin/plsql/utils/perl/sqlutils.pm line 197
### Upgrade aborted
I granted SYSDBA to SYS schema and tried. That did not work either.
Any suggestions?
Thanks in advance...
-- Shravan

Shravan
Are you sure the PORTAL schema password is portal. By default on a 902 install it is a scrambled sequence of letters that you can figure out by looking up the entry in OID. This value is different from the Portal user as stored in OID. Check out the password by logging onto the account with sqlplus. Don't change the password from the sys account if you find out that it is not portal. Look it up in OID and use that value. I would check the sys password by the same technique to be absolutely sure it is correct.
Check the upgrade first by running
perl upgrade.pl -precheck
If you are sure that both of your passwords are correct then I would get in touch with support and log a TAR for addition assistance.
Regards

R3 - Repository Upgrade failed

Hi,
AIX5, EM10gR2 upgrade to R3.
(Fresh installation of R2, applied patch 4329444, proceed with R3 upgrade)
At the Configuration Assistants screen:
"Repository Upgrade failed"
$ cat configToolFailedCommands
# Copyright (c) 1999, 2007, Oracle. All rights reserved.
oracle.sysman.emcp.oms.RepositoryPatchUpgrade -verbose
oracle.sysman.emcp.oms.OmsPatchUpgrade -configureOms
oracle.sysman.emcp.aggregates.ConfigPlugIn
oracle.sysman.emcp.oms.StartOMS -configureOms
oracle.sysman.ccr.configCCR.ConfigCCRPlugIn
Not sure what to do.
Any hints how to proceed?
Thx,
Dobby

Same problem but on RHEL4 when trying to upgrade to 10.2.0.3. Fresh install with database already 10.2.0.3 and OMS was installed with option "existing DB".
Database and listener were left running but all other processes were shutdown with opmnctl stopall.
Any ideas?
This is the end of $OMS_HOME/sysman/log/emoms.trc:
2007-10-04 10:23:14,204 [Job Dispatcher Thread] WARN jdbc.ConnectionCache _getConnection.353 - Got a fatal exeption when getting a connection; Error code = 17002; Cleaning up cache and retrying
2007-10-04 10:23:14,220 [Job Dispatcher Thread] ERROR em.jobs preTask.2292 - Cannot get id: Io exception: The Network Adapter could not establish the connection
2007-10-04 10:23:18,248 [NotificationMgrThread] WARN jdbc.ConnectionCache _getConnection.352 - Io exception: The Network Adapter could not establish the connection
java.sql.SQLException: Io exception: The Network Adapter could not establish the connection
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:137)
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:174)
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:286)
at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:327)
at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java:433)
at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:150)
at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtension.java:31)
at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:571)
at oracle.jdbc.pool.OracleDataSource.getConnection(OracleDataSource.java:217)
at oracle.jdbc.pool.OracleConnectionPoolDataSource.getPhysicalConnection(OracleConnectionPoolDataSource.java:108)
at oracle.jdbc.pool.OracleConnectionPoolDataSource.getPooledConnection(OracleConnectionPoolDataSource.java:76)
at oracle.jdbc.pool.OracleImplicitConnectionCache.makeCacheConnection(OracleImplicitConnectionCache.java:1344)
at oracle.jdbc.pool.OracleImplicitConnectionCache.getCacheConnection(OracleImplicitConnectionCache.java:435)
at oracle.jdbc.pool.OracleImplicitConnectionCache.getConnection(OracleImplicitConnectionCache.java:330)
at oracle.jdbc.pool.OracleDataSource.getConnection(OracleDataSource.java:285)
at oracle.jdbc.pool.OracleDataSource.getConnection(OracleDataSource.java:253)
at oracle.sysman.util.jdbc.ConnectionCache._getConnection(ConnectionCache.java:336)
at oracle.sysman.util.jdbc.ConnectionCache._getConnection(ConnectionCache.java:322)
at oracle.sysman.util.jdbc.ConnectionCache.getUnwrappedConnection(ConnectionCache.java:575)
at oracle.sysman.emSDK.svc.conn.FGAConnectionCache.getFGAConnection(FGAConnectionCache.java:207)
at oracle.sysman.emSDK.svc.conn.ConnectionService.getSystemConnection(ConnectionService.java:1304)
at oracle.sysman.emdrep.notification.NotificationMgr.getConnection(NotificationMgr.java:403)
at oracle.sysman.emdrep.notification.NotificationMgr.run(NotificationMgr.java:1453)
2007-10-04 10:23:18,251 [NotificationMgrThread] WARN jdbc.ConnectionCache _getConnection.353 - Got a fatal exeption when getting a connection; Error code = 17002; Cleaning up cache and retrying

DAC repository creation.....

Hi All,
I am new to DAC. I am not talking about BI Apps only DAC.
What I am trying to achieve: Create an informatica mapping, add it to dac, schedule a full load, & then incremental load........
I have only Oracle XE, IPC 9.0.1, and DAC 10.1.3.4.1.
Can I use DAC only as a scheduling tool for running informatica mappings?? I am facing trouble in creating a new dac repository.....
Thanks,
DK

thanks a lot for the help
i created a new Datawarehouse ,used it as target
repeated all the steps that involved details about the target datawarehouse
i'm still getting an Error
the significant lines are:
56 SEVERE Fri Aug 23 14:25:21 GMT 2013 MESSAGE:::No value for @DAC_SOURCE_PRUNED_REFRESH_TIMESTAMP available!
EXCEPTION CLASS::: com.siebel.analytics.etl.converter.evaluator.EvaluationException
58 SEVERE Fri Aug 23 14:25:22 GMT 2013
ANOMALY INFO::: DataWarehouse:TRUNCATE TABLE W_ETL_RUN_S
ORA-00942: table or view does not exist
MESSAGE:::ORA-00942: table or view does not exist
can you help ?

Unable to import DAC repository

Hello all,
I am installing BIA7.9.5 on R12.
Now I want to configure the DAC but when I go to:
Tools -> Dac repository Management -> impoirt
And choose the Oracle R12 application.
And check truncate tables
Now when I press OK nothing happens.
I still see the same screen, no error of no other things. It just looks like that the button isn't working.
I configured config.bat with the good JAVA_HOME and DAC_HOME.
Does anyone had an idea why this occurs?

I had the same problem because on my client machine i had installed the latest version of Java because the requirements stated JDK 1.5 or higher. However it seems you get this "button does nothing" bug with 1.6. I installed the terminal release of 1.5 and edited my config file.
On your client edit \DAC\config.bat
REM set JAVA_HOME=C:\app\Java\jdk1.6.0_12
set JAVA_HOME=C:\app\Java\jdk1.5.0_17
The idea for this fix came for this post
DAC Client 7.9.5.1 is not compatible with Java SDK 1.6.0_12 - use 1.5.0_17
Re: DAC Client 7.9.5.1 is not compatible with Java SDK 1.6.0_12 - use 1.5.0_17

No response when trying to Importing Metadata into the DAC Repository

Hello,
I just installed OBIEE and OBIAPP as well as Informatica and am now trying to login to DAC client to import metadata into the DAC repository. So Tools->DAC Repository Management>Import. After I checked Universal and Siebel 8.0 and clicked OK button, there is nothing happening. I can actually still click on the Cancel button to close the Import window.
Has anyone experienced this before? Really appreciate some help here.
Thanks,
Harry

I have exactly same problem. did you manage to solve it?

Recommendations for Infa/DAC repository databases?

Hi Guys,
Looking for any recommendations on how to setup an 11g database instance for Informatica/DAC repository and domain databases.
Looking for init.ora recommendations, memory settings, block size or any other tuning that people have found helpful.
I have the guidelines from Oracle for the DataWarehouse, but looking for anything specific to DAC/Informatica.
Thanks!!!

Please check below documents (not specific to 11g but helps) from support.oracle.com
781927.1
1287167.1

10.2.0.1.1 upgrade to 10.2.0.2 failed in Repository Upgrade.

RHEL4.8 x86
10.2.0.1.1 upgrade to 10.2.0.2 failed in Repository Upgrade.
Applying patch to OMS. Configuration Assistants failed in "Repository Upgrade".
OracleHomes/oms10g/cfgtoollogs/configToolFailesCommands shows:
oracle.sysman.emcp.oms.RepositoryPatchUpgrade -verbose
oracle.sysman.emcp.oms.OmsPatchUpgrade -configureOms
oracle.sysman.emcp.oms.ConfigPlugIn
Any idea?

Check at the log OMSHOME/sysman/log/*.err/

DAC Repository upgrade

Similar Messages

Maybe you are looking for