R12 Database Version while upgrade

Hi All,
I am planning an upgrade from 11.5.9 CU1 (DB 9.0.2.8) to 12.1.3(DB 11gR2).
I am aware that as apart of upgrade I need to upgrade my DB to 10gR2 and then apply the upgrade driver.
But here is my question can I upgrade the database from 9.0.2.8 to 11gR2 (directly) and then apply the upgrade driver for 12.1.1 and then perform the 12.1.1 to 12.1.3 upgrade, as the upgrade manual says that the DB should be upgraded "least" to 10gR2 so upgrading to 11g shouldn't be an issue logically because any way 11.5.9 base release is not certified with 10g and one need to apply the CU2 patch for it which I won't be applying.
This way I can possibly reduce the downtime required to upgrade database first from 9i to to 10g and then to 11g.
Any body here if have taken similar exercise and can throw some light and advise that will be a help.
TIA!

Hi,
But here is my question can I upgrade the database from 9.0.2.8 to 11gR2 (directly) and then apply the upgrade driver for 12.1.1 and then perform the 12.1.1 to 12.1.3 upgrade, as the upgrade manual says that the DB should be upgraded "least" to 10gR2 so upgrading to 11g shouldn't be an issue logically because any way 11.5.9 base release is not certified with 10g and one need to apply the CU2 patch for it which I won't be applying.
This way I can possibly reduce the downtime required to upgrade database first from 9i to to 10g and then to 11g.Please see
Re: EBS 11.5.9 to 12.1.1 upgrade
Upgrade 11.5.9 to 12.1.2
11.5.9 Upgrade Timings
Thanks
Edited to remove the direct upgrade to 11gR2

Similar Messages

ARM approval error after upgrading to SP14: Database error while using the secure store.

Dear GRC experts,
After upgrading GRC 10 to SP14, assigning manual passwords during the approval of a request, the approval process is failing.
Here is the scenario; your advice will be appreciated.
Task: Manually assign passwords to multiple systems contained in the request
Where: On the access request, go to “User System Details” tab
Issue: After approving/submitting the request, the error “Database error while using the secure store” is generated
Logs: Nothing on transactions SLG1 or ST22; however ST11 shows the error attached below:
This is the failed approval of the request:
Other scenarios executed as a workaround, and passed the password assignment this time:
The approval will work if only one password is assigned to any of the given systems. The rest of the systems get an auto-generated
password.
ARM also accepts multiple passwords when the requestor assigns passwords on the “User System Details” prior submitting a
request. The GRC admin can approve once reached for system approval.
AS FYI, “Confirm Password” is only required when creating the request but not on any other stage.
System information:
-Netweaver 7
-GRCFND_A SP14
-GRCPINW SP13
Regards,
Gustavo

SAP just delivered a note to fix this issue. The number is 2022294.

Oracle Report Failing After Database Version Upgrade

Hi,
I have function code created in RDF file of oracle reports 10g as below-
create or replace function clobblobtest (TMP_MID varchar2) return varchar is
missed_text varchar2(1000) := '';
v_time_stamp date;
v_end_time date;
cursor c1(c_time_stamp in date,
          c_mid in varchar2) is
       select mn.TEXT from msgnotes mn
where mn.mid=c_mid
      and mn.create_date >= c_time_stamp;
cursor c2(c_time_stamp in date,
          c_mid in varchar2,
          c_end_time in date) is
       select mn.TEXT from msgnotes mn
where mn.mid=c_mid
      and mn.create_date >= c_time_stamp
      and mn.create_date <= c_end_time;
begin
IF ('1' = 'INWARD RETURN') then
    select bbi into missed_text from mtf1000 where mid=TMP_mid;
    ELSIF '1'='QPH Missed' then
Select max(nj.update_date) into v_time_stamp
from newjournal nj
where nj.mid=TMP_mid and nj.status = 'CTOVRQ';
for i in c1(v_time_stamp,TMP_mid) loop
missed_text:=missed_text||' '||i.text;
END Loop;
ELSIF ('Rejected'='Rejected' OR 'REJECTED'='REJECTED') then
IF ('TERMINATED' in ('TERMINATED')) THEN
Select min(nj.update_date),max(nj.ENDDATE) into v_time_stamp,v_end_time
from newjournal nj
where nj.mid=TMP_mid and nj.actionid2='16' and nj.actionid1 is null;
for i in c2(v_time_stamp,TMP_mid,v_end_time) loop
missed_text:=missed_text||' '||i.text;
END Loop;
ELSE
Select max(nj.update_date) into v_time_stamp
from newjournal nj
where nj.mid=TMP_mid and nj.status = 'UNSETLED';
for i in c1(v_time_stamp,TMP_mid) loop
missed_text:=missed_text||' '||i.text;
END Loop;
END IF;
ELSE missed_text := null;
END IF;
return(missed_text);
End;
Note:- Text column from table msgnotes is of datatype CLOB.
I have executed report having this function before oracle upgrade and it works fine.
But when i am trying to execute report after oracle version upgrade from 11.2.0.3.0 to 11.2.0.4.0 with same data report fails with runtime error Rep-1401: '' Fatal PL/SQL Error.
With New version we tried to typecast Text column from clob to varchar and executed report then it works... but report runs on old version without any explicit typecasting.
Please note when i run and call this funtion from sql developer with upgraded database version it works fine.
Please advise.

This error can possibly depend on the fact that the PL/SQL engines are in different versions. When using SQL Developer you use the PL/SQL engine in the database. When using Oracle Reports you use the PL/SQL engine in the Oracle Reports Server (Web Logic Server even maybe). These versions - in the Forms and Reports realm - are different (read: a lower version) than the PL/SQL engine in the database.
If I check what version I have in Oracle Forms, as an example, I get 11.1.0.7.0 (Help in the Oracle Forms Builder menu) but in the database I have (select * from product_component_version;) 11.2.0.3.0.
That COULD be your issue...how to fix it I am not sure...

My iMessages don't work since updating. It says the Messages database is being upgraded, please wait while it finishes or Quit Messages and relaunch it later. How do I get them working again?

My iMessages don't work since updating. It says the Messages database is being upgraded, please wait while it finishes or Quit Messages and relaunch it later. How do I get them working again?

Back up all data.
Quit Messages if it’s running. Force quit if necessary. Relaunch it and test after each of the following steps. If the problem isn't resolved, quit again and go on to the next step.
Step 1
Make sure you know the ID and password you use with iMessage. Launch the Keychain Access application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad and start typing the name.
Select the login keychain from the list on the left side of the Keychain Access window. If your default keychain has a different name, select that.
If the lock icon in the top left corner of the window shows that the keychain is locked, click to unlock it. You'll be prompted for the keychain password, which is the same as your login password, unless you've changed it.
Right-click or control-click the login entry in the list. From the menu that pops up, select
          Change Settings for Keychain "login"
In the sheet that opens, uncheck both boxes, if not already unchecked.
From the menu bar, select
          Keychain Access ▹ Preferences ▹ First Aid
If the box marked
          Keep login keychain unlocked
is not checked, check it.
Select
          Keychain Access ▹ Keychain First Aid
from the menu bar and repair the keychain.
From the Category list in the lower left corner of the window, select My Certificates. Look carefully at the list of certificates in the right side of the window. If any of them is marked with a red "X" as expired or invalid, delete it. Also delete all items with "iMessage" or "com.apple.idms" in the name, whether valid or not.
From the menu bar, select
          Keychain Access ▹ Preferences... ▹ Certificates
There are three menus in the window. Change the selection in the top two to Best attempt, and in the bottom one to CRL.
Log out and log back in.
Step 2
Hold down the option key and select
          Go ▹ Library
from the Finder menu bar. Move the following items from the Library folder to the Trash (some may not exist):
          Containers/com.apple.corerecents.recentsd
          Caches/com.apple.Messages
          Caches/com.apple.imfoundation.IMRemoteURLConnectionAgent
          Containers/com.apple.iChat
          Containers/com.apple.soagent
          IdentityServices
Leave the Library folder open. Log out and log back in.
Step 3
Go back to the Finder and move the following item from the open Library folder to the Desktop:
          Messages
Note: you are not moving the Messages application. You’re moving a folder named “Messages.”
If Messages now works, delete the Messages folder on the Desktop. Otherwise, quit Messages again. Put back the folder you moved, overwriting the newer one that may have been created in its place.
Step 4
In the Preferences subfolder, there may be several files having names that begin with any of the following strings:
          com.apple.iChat
          com.apple.ids
          com.apple.imdsmsrecordstore
          com.apple.imessage
          com.apple.imservice
Move them all to the Desktop. There may also be a file with the name "com.apple.imagent.plist". Move that to the Trash.
Also in the Preferences folder, there's a subfolder named "ByHost". Open it and do the same thing.
Log out and log back in. Test again. This time Messages should perform normally, but your settings will be lost. You may be able to put back some of the files you moved to the Desktop in this step. Relaunch and test after each one. Eventually you should find one or more that causes Messages to malfunction. Delete those files and recreate whatever settings they contained.
If the issue is still not resolved, quit Messages again and put all the items you moved to the Desktop back where they were. You don’t need to replace the items you moved to the Trash. Stop here and post your results.
If you later decide that you don’t like the results of Steps 3 and 4, you can undo them completely by quitting Messages and restoring the items you deleted in those steps from your backup.

P6.2.1 upgrade to P6.7.0 database version miss match

Hello,
I was using Primavera 6.21 and i made an upgrade to Primavera 6.7.0
When i run my PMDB data base the following message pops:
The application and database versions do not match. Click Exit to close the application.
Primavera P6 7.0.0
Expected database version: PMDB,0700.0001.0001
Current database version: PMDB,0602.0005.0001
I am using SQL Server 2005
Can you help
Thank you

That means that your database was not upgraded. You need to upgrade the application and the database.
Run dbsetup.bat (in your media folder) to upgrade your database.

ORA-01092 error while upgrading database from 9.2.0.6 to 10.2.0.1

Hi ,
Am getting ORA-01092 error while upgrading database to 10.2.0.1 from 9.2.0.6
I executed the catupgrd.sql successfully and recompiled invaild objects.
After that i tried to startup the database,but am getting the error:
sql>startup
oracle instance started
database mounted
ORA-01092 : Oracle instance terminated. Disconnection forced
I checked alert log file.
I am getting the following errors
Errors in file /u01/......./udump/VIS_ora/7179.trc
ORA-00604: error occurred at recursive SQL level 1
ORA-00607: internal error occurred while making change to a datablock
ORA-00600: internal error code, arguments [4194],[70] ,[39] [ ] []
Error 604 happened during database open . Shutting down database
instance terminated by USER pid =7179
ORA-01092 error Signaled during alter database open
Is there any block corruption? could u please share the solution for these errors?

Hi;
You are hitting ORA-00600: error which mean you may need to work oracle support for your issue.Pelase check below note if its not help i suggest rise sr
Troubleshoot an ORA-600 or ORA-7445 Error Using the Error Lookup Tool [ID 153788.1]
Regard
Helios

How to deal with time zone while upgrading the database?

Hi,
How to deal with time zone while upgrading the database?
Thanks
Edited by: user12135020 on Jul 4, 2011 3:06 AM

Hello,
I answered to a Wrong post.
Best regards,
Jean-Valentin
Edited by: Lubiez Jean-Valentin on Jul 4, 2011 12:15 PM

ORA-03113: Error while upgrading the Database from 11.1.0.6 to 11.1.0.7

Hi,
I am trying to upgrade the database from 11.1.0.6 to 11.1.0.7 on OEL operating system.
After applying the patch "6890831" when trying to start the database using "Startup Upgrade" command I am getting the below error.
ORA-03113: end-of-file on communication channel
Process ID: 20826
Session ID: 170 Serial number: 3
I am getting the same error when trying to create the new database using "DBCA".
Please provide me the probable outcomes.
Thanks
Amith

Below entries found in alert_orcl.log file
MMNL started with pid=15, OS id=20571
starting up 1 shared server(s) ...
ORACLE_BASE from environment = /u01/app/oracle
Thu Dec 03 20:11:11 2009
ALTER DATABASE MOUNT
Errors in file /u01/app/oracle/diag/rdbms/orcl/orcl/trace/orcl_mman_20557.trc:
ORA-27103: internal error
Linux-x86_64 Error: 11: Resource temporarily unavailable
Additional information: -1
Additional information: 1
MMAN (ospid: 20557): terminating the instance due to error 27103
Instance terminated by MMAN, pid = 20557
Below entries found in the Trace file generated
error 27103 detected in background process
ORA-27103: internal error
Linux-x86_64 Error: 11: Resource temporarily unavailable
Additional information: -1
Additional information: 1
*** 2009-12-03 20:11:14.727
MMAN (ospid: 20557): terminating the instance due to error 27103

Proxy User - Forms 11.1.2 and Oracle Database (version 10.1.0.5) ??

Hi,
we are migrating from Forms 6i to 11.1.2. Our database version is very old (Enterprise Edition, version 10.1.0.5) because this is the latest version of the DB that Forms 6i runs, and we will migrating to 11g in phases. So 6i and 11g will co-exists for a while (accesing the same DB).
I am trying to use proxy users feature to login to database.
So I did this:
- I created a user PROXY_USR to be the proxy user:
SQL> create user PROXY_USR identified by PROXY_PASW;*
- I grant create session for the user:
SQL> grant create session to PROXY_USR;*
- I changed the application users (eg APPUSER01), to connect via proxy user:
SQL> alter user APPUSER01 grant connect through PROXY_USR;*
The comand in Forms module to login is:
+LOGON('PROXY_USR[APPUSER01]','PROXY_PASW@DB01');+*
The logon built is being performed and the connection being made, without erros.
But when I verify in what user the application is logged on, the result is not
what was expected:
I did the follwing PL/SQL inside Form module:
begin*
select user into v_user_DB from dual;*
MESSAGE('User Connected: '||v_user_DB,ACKNOWLEDGE);*
exception*
when others then*
MESSAGE('ERR: '||SQLERRM,ACKNOWLEDGE);*
end;*
The result from this select, is PROXY_USR and not APPUSER01 (that would be the correct):
*>>Result: "User Connected: PROXY_USR"*
Some more commands that were also performed inside Forms module:
begin+
select sys_context('userenv','current_user') v_current_usr from dual+
MESSAGE('Current User: '||v_current_usr,ACKNOWLEDGE);+
exception+
when others then+
MESSAGE('ERR: '||SQLERRM,ACKNOWLEDGE);+
*>>Result: "User Connected: PROXY_USR"*
begin+
select sys_context('userenv','proxy_user') v_proxy_user from dual;+
MESSAGE('Current User: '||v_proxy_user,ACKNOWLEDGE);+
exception+
when others then+
MESSAGE('ERR: '||SQLERRM,ACKNOWLEDGE);+
*>>Result: "Proxy User: "*
OBS: when a connect via SQL*Plus, in a 11g database (Express), and run the commands above, the results are OK. The
APPUSER01 is returned.
Any ideas ?? I will open a SR in Metalink, but I think they will first request a database upgrade,
which is not feasible for us at the moment ...
Thanks in Advance.
Franco

Unfortunately besides trying on a certified combination (maybe use the Developer Database VM and import the required schemas for trial) and going through the documentation at http://docs.oracle.com/cd/E24269_01/doc.11120/e24477/sso.htm I can't offer more. I don't have a 10gR1 database anymore and also I don't have OID to play with.
cheers

The SYSVAL table entry for the database version (16) does not match the required version

We upgraded from Tidal Enterprise Scheduler (TES) 5.31 to 6.1 on fresh Windows x64 2008 R2 servers. I did a fresh install but our DBA restored a copy of our database from pre-prod which was at 5.31. I get the error below. Note, SQL went from 2005 to 2012 during this upgrade. Do I need to change a value in this table to reflect the SQL change?
[04/29 12:47:14:198]:TIDAL Enterprise Scheduler: version 6.1.0.133
[04/29 12:47:14:198]:Java version: 1.8.0
[04/29 12:47:14:198]:Java Virtual Machine version: 25.0-b70
[04/29 12:47:14:198]:Start Time : 04/29/14 12:47:14:198
[04/29 12:47:14:198]:----------------------------------------------------------------------------
[04/29 12:47:14:198]:Database URL :jdbc:sqlserver://SQL2012-Host:1433;responseBuffering=adaptive
[04/29 12:47:14:198]:Database Driver :com.microsoft.sqlserver.jdbc.SQLServerDriver
[04/29 12:47:14:198]:Maximum number of log files = 100
[04/29 12:47:14:198]:Added a LogFile called 'RegularFile'
[04/29 12:47:14:198]:LogManager: setting default log
[04/29 12:47:14:214]:Retrieved a LogFile called 'RegularFile'
[04/29 12:47:14:495]:MessageBroker: Instantiated TcpTransportServer (URI = tcp://0.0.0.0:6215)
[04/29 12:47:16:975]:Retrieved a LogFile called 'RegularFile'
[04/29 12:47:17:272]:The SYSVAL table entry for the database version (16) does not match the required version (23). Shutting down.
[04/29 12:47:20:282]:
[04/29 12:47:20:282]:
[04/29 12:47:20:282]:Shutting down the application

I had this error last night while applying a patch to 6.0. However in my case the version was 21 versus a required version of 23.
As far as i know 6.1 is not compatible with the 5 db schema, so you will need an update / migration plan for the db also.

Missing features while upgrading to sharepoint2013

While upgrading i faced two issues:
1. Found a missing feature Id = [dc98d4f8-2307-4fe4-9f9c-5b9d97bce640], Name = [Lab04 Feature1], Description = [], Install Location = [Lab04_Feature1
2. WebPart class [6fcd2d02-416d-6df5-d11b-992a0dc48370] (class [JSharepoint.JSFile.JSFile] from assembly [JSharepoint, Version=1.0.0.0, Culture=neutral, PublicKeyToken=62e6c3f22721431c])
is referenced [2] times in the database [WSS_Content_02], but is not installed on the current farm. Please install any feature/solution which contains this web part.
i run the following query against database but query returns null
SELECT * FROM WSS_Content_2007.dbo.Features WHERE FeatureId = ’75a0fea7-cd50-401e-af0e-782f3662a299′
SELECT * FROM WSS_Content_2007.dbo.WebParts WHERE tp_WebPartTypeId like ’68ec641-8c6a-1cc6-6465-185094919a93′
is there any other way the fix these issues

Let me know if you can help in below issue;
I am trying to migrate SP 2010 to SP 2013 using contend db upgrade method.
Before runing Test-SPContentDatabase command I deployed all the custom wsps.
But still I am getting feature not found. No change in GUIDs.
I deployed branding feature in compitible mode and rest of other features are in native mode.
upgrade error log shows both types of features are missing.
But when I create Site Collection on default content database then I can see custom features are
avaiable.
I had followed same steps as you described in your post except one change in wsp deployment.
I had deployed branding wsp in compatible mode (14) and rest of features are native mode (15)
with same GUID. Still I am getting both type of features marked as missing.
As per your experiecne, at least in my case branding feature should not be marked as missing as installed sp 2010 version. But I can see under missing feature error.
My next question: Is that mean we can't migrate SP 2010 Content database having customization directly to native mode and has to follow compatible mode?
Thanks in advance
- Sudarshan S Vatturkar

Deployment error while upgrading from WLS6.1 to WLS9.1

We are upgrading from Weblogic 6.1 to Weblogic 9.1.
We are facing with two issues while upgrading.
1. We are having a start up servlet and that servlet uses Database appender and uses log4j. This class is inside a jar file and this jar is part of the ear file.
The admin server starts but with the following error.
log4j:ERROR Could not create an Appender. Reported error follows.
java.lang.ClassNotFoundException: com.tuiuk.greenfield.foundation.logging.log4j.Dat
abaseAppender
at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericCla
ssLoader.java:222)
at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoa
der.java:195)
at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClassLoa
der.java:130)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:164)
at org.apache.log4j.helpers.Loader.loadClass(Loader.java:160)
at org.apache.log4j.xml.DOMConfigurator.parseAppender(DOMConfigurator.java:
164)
at org.apache.log4j.xml.DOMConfigurator.findAppenderByName(DOMConfigurator.
java:140)
at org.apache.log4j.xml.DOMConfigurator.findAppenderByReference(DOMConfigur
ator.java:153)
at org.apache.log4j.xml.DOMConfigurator.parseChildrenOfLoggerElement(DOMCon
figurator.java:415)
at org.apache.log4j.xml.DOMConfigurator.parseRoot(DOMConfigurator.java:384)
at org.apache.log4j.xml.DOMConfigurator.parse(DOMConfigurator.java:783)
at org.apache.log4j.xml.DOMConfigurator.doConfigure(DOMConfigurator.java:66
6)
at org.apache.log4j.xml.DOMConfigurator.doConfigure(DOMConfigurator.java:61
6)
at org.apache.log4j.xml.DOMConfigurator.doConfigure(DOMConfigurator.java:60
2)
at org.apache.log4j.helpers.OptionConverter.selectAndConfigure(OptionConver
ter.java:460)
at org.apache.log4j.LogManager.<clinit>(LogManager.java:113)
at org.apache.log4j.Category.getInstance(Category.java:514)
at org.apache.commons.logging.impl.Log4JCategoryLog.<init>(Log4JCategoryLog
.java:104)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorA
ccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingCons
tructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:494)
at org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImp
l.java:525)
at org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImp
l.java:272)
at org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImp
l.java:246)
at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:395)
at com.bea.console.preferences.spi.FilePreferencesProvider.<clinit>(FilePre
ferencesProvider.java:53)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:164)
at com.bea.portlet.prefs.spi.ProviderFactory.createInstance(ProviderFactory
.java:78)
at com.bea.portlet.prefs.spi.ProviderFactory.setDefaultProviderClass(Provid
erFactory.java:47)
at com.bea.portlet.prefs.spi.IPreferenceStore$Factory.registerDefaultProvid
er(IPreferenceStore.java:128)
at com.bea.netuix.servlets.manager.SingleFileServlet.init(SingleFileServlet
.java:113)
at javax.servlet.GenericServlet.init(GenericServlet.java:256)
at weblogic.servlet.AsyncInitServlet.initDelegate(AsyncInitServlet.java:94)
at weblogic.servlet.internal.WebAppServletContext$AsyncInitRequest.run(WebA
ppServletContext.java:1641)
at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManage
rImpl.java:518)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:179)
log4j:ERROR Could not parse input source [org.xml.sax.InputSource@5d8e63].
java.lang.NullPointerException
at java.util.Hashtable.put(Hashtable.java:396)
at org.apache.log4j.xml.DOMConfigurator.findAppenderByName(DOMConfigurator.
java:141)
at org.apache.log4j.xml.DOMConfigurator.findAppenderByReference(DOMConfigur
ator.java:153)
at org.apache.log4j.xml.DOMConfigurator.parseChildrenOfLoggerElement(DOMCon
figurator.java:415)
at org.apache.log4j.xml.DOMConfigurator.parseRoot(DOMConfigurator.java:384)
at org.apache.log4j.xml.DOMConfigurator.parse(DOMConfigurator.java:783)
at org.apache.log4j.xml.DOMConfigurator.doConfigure(DOMConfigurator.java:66
6)
at org.apache.log4j.xml.DOMConfigurator.doConfigure(DOMConfigurator.java:61
6)
at org.apache.log4j.xml.DOMConfigurator.doConfigure(DOMConfigurator.java:60
2)
at org.apache.log4j.helpers.OptionConverter.selectAndConfigure(OptionConver
ter.java:460)
at org.apache.log4j.LogManager.<clinit>(LogManager.java:113)
at org.apache.log4j.Category.getInstance(Category.java:514)
at org.apache.commons.logging.impl.Log4JCategoryLog.<init>(Log4JCategoryLog
2. The second error is
The managed server starts without any problem. Using the appication, we connect to 3rd party library to validate payment details. This 3rd party jar is also part of the ear file.
Basically the ear contains all the ejb jars, 3rd party jars and war files.
In this case we are getting the following error.
com.tuiuk.greenfield.template.navigation.web.handler.GreenfieldExceptionHandler
com.tuiuk.greenfield.foundation.exception.GreenfieldRuntimeException: Locating the PaymentManager Nested exception is:
     java.rmi.RemoteException: EJB Exception: ; nested exception is:
     java.lang.NoClassDefFoundError: com/datacash/logging/LogListener
com.tuiuk.greenfield.foundation.exception.GreenfieldRuntimeException: Locating the PaymentManager Nested exception is:
     java.rmi.RemoteException: EJB Exception: ; nested exception is:
     java.lang.NoClassDefFoundError: com/datacash/logging/LogListener
java.rmi.RemoteException: EJB Exception: ; nested exception is:
     java.lang.NoClassDefFoundError: com/datacash/logging/LogListener
     at weblogic.ejb.container.internal.EJBRuntimeUtils.throwRemoteException(EJBRuntimeUtils.java:95)
     at weblogic.ejb.container.internal.BaseEJBObject.handleSystemException(BaseEJBObject.java:713)
     at weblogic.ejb.container.internal.BaseEJBObject.handleSystemException(BaseEJBObject.java:681)
     at weblogic.ejb.container.internal.BaseEJBObject.postInvoke1(BaseEJBObject.java:447)
     at weblogic.ejb.container.internal.StatelessEJBObject.postInvoke1(StatelessEJBObject.java:72)
     at weblogic.ejb.container.internal.BaseEJBObject.postInvokeTxRetry(BaseEJBObject.java:374)
     at com.tuiuk.greenfield.service.payment.datacash.ejb.PaymentServiceEJB_hlf8l4_EOImpl.getCardType(PaymentServiceEJB_hlf8l4_EOImpl.java:288)
     at com.tuiuk.greenfield.template.orchestration.book.PaymentImpl.getCardType(PaymentImpl.java:190)
     at com.tuiuk.greenfield.template.orchestration.book.BookOrchestratorImpl.getCardType(BookOrchestratorImpl.java:2044)
     at com.tuiuk.greenfield.template.navigation.web.action.book.CheckPaymentCardAction.executeAction(CheckPaymentCardAction.java:109)
     at com.tuiuk.greenfield.template.extension.navigation.struts.action.BaseAction.execute(BaseAction.java:202)
     at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:484)
     at com.tuiuk.greenfield.template.navigation.web.processor.book.BeachBookRequestProcessor.processActionPerform(BeachBookRequestProcessor.java:81)
     at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:274)
     at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1482)
     at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:525)
     at com.tuiuk.greenfield.brand.th.navigation.action.THUserInterfaceFactory.doPost(THUserInterfaceFactory.java:105)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:763)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
     at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:225)
     at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:127)
     at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:272)
     at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:165)
     at weblogic.servlet.internal.RequestDispatcherImpl.invokeServlet(RequestDispatcherImpl.java:493)
     at weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:245)
     at org.apache.struts.action.RequestProcessor.doForward(RequestProcessor.java:1069)
     at org.apache.struts.action.RequestProcessor.processForwardConfig(RequestProcessor.java:455)
     at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:279)
     at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1482)
     at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:525)
     at com.tuiuk.greenfield.brand.th.navigation.action.THUserInterfaceFactory.doPost(THUserInterfaceFactory.java:105)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:763)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
     at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:225)
     at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:127)
     at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:272)
     at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:165)
     at weblogic.servlet.internal.RequestDispatcherImpl.invokeServlet(RequestDispatcherImpl.java:493)
     at weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:245)
     at org.apache.struts.action.RequestProcessor.doForward(RequestProcessor.java:1069)
     at org.apache.struts.action.RequestProcessor.processForwardConfig(RequestProcessor.java:455)
     at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:279)
     at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1482)
     at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:525)
     at com.tuiuk.greenfield.brand.th.navigation.action.THUserInterfaceFactory.doPost(THUserInterfaceFactory.java:105)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:763)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
     at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:225)
     at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:127)
     at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:272)
     at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:165)
     at weblogic.servlet.internal.RequestDispatcherImpl.invokeServlet(RequestDispatcherImpl.java:493)
     at weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:245)
     at org.apache.struts.action.RequestProcessor.doForward(RequestProcessor.java:1069)
     at org.apache.struts.action.RequestProcessor.processForwardConfig(RequestProcessor.java:455)
     at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:279)
     at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1482)
     at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:525)
     at com.tuiuk.greenfield.brand.th.navigation.action.THUserInterfaceFactory.doPost(THUserInterfaceFactory.java:105)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:763)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
     at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:225)
     at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:127)
     at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:272)
     at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:165)
     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3150)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
     at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:1973)
     at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:1880)
     at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1310)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:179)
Caused by: java.lang.NoClassDefFoundError: com/datacash/logging/LogListener
     at com.tuiuk.greenfield.service.payment.datacash.ejb.PaymentManagerEJB.getPreAuthorisationFacade(PaymentManagerEJB.java:255)
     at com.tuiuk.greenfield.service.payment.datacash.ejb.PaymentManagerEJB.getCardType(PaymentManagerEJB.java:158)
     at com.tuiuk.greenfield.service.payment.datacash.ejb.PaymentServiceEJB_hlf8l4_EOImpl.getCardType(PaymentServiceEJB_hlf8l4_EOImpl.java:274)
     ... 66 more
I have added explicitly this 3rd party jar in to the manifest file of the ejb jar that is looking for this jar.
Can you please throw some light in to this.

Hi Sebastiaan,
which database version are you using?
Anyway I would suggest that you get in contact with your DBA and he with Oracle Support.
Based on the bug description this error has something to do with your database and DBMS_STATS (used to calculate statistics for your data) and not really with APEX itself.
Oracle Support should be able to help you to find out which database patch you have to install.
Regards
Patrick
My Blog: http://www.inside-oracle-apex.com
APEX Plug-Ins: http://apex.oracle.com/plugins
Twitter: http://www.twitter.com/patrickwolf

Error while upgrading Oracle Portal to 10.1.4.

While upgrading Oracle Portal to 10.1.4 , I am getting the following error.
Error: Database version 9.0.1.5.1 is not supported
MRUA detected an error at C:\oracleportalupgrade\mrua_051020\mrua\mrua.pl line 212.
Please let me know how can I resolve this issue.

There is no WSRP container created as a part of the AS 10.1.2.0.2 or Portal 10.1.4 setup (that means there is no WSRP directory below $ORACLE_HOME/j2ee by derfault).
You need to create a brand new application server container, either in the same oracle home as portal or (as we are doing according to advice from oracle) create a new AS 10.1.2.0.2 AS oracle home for just J2EE (not portal) and then create a container for your WSRP portlets -- we called ours OC4J_WSRP. This is the step that will create a directory under $ORACLE_HOME/j2ee (in our case $ORACLE_HOME/j2ee/OC4J_WSRP).
After you have your new container (OC4J_WSRP), you need to configure this container to support WSRP. First you need to download the "Java Portlet Container for Standards" from http://www.oracle.com/technology/products/ias/portal/pdk.html (this does not come with the Portal 10.1.4 installation).
Download "Download the Java Portlet Container (JSR 168)":
http://download.oracle.com/otndocs/tech/ias/portal/files/portlet-container.zip
This will get you portlet-container.zip.
Extract this zip file. One of the files you will have is wsrp-install.jar.
Then log into the box where your new OC4J_WSRP container is setup (it is really important that you have not changed the default configuration of this new app server container or deployed any applications before running the next step) and ...
1. copy wsrp-install.jar into $ORACLE_HOME/j2ee/OC4J_WSRP
2. cd $ORACLE_HOME/j2ee/OC4J_WSRP
3. run "java -jar wsrp-install.jar"
4. restart your app server that contains OC4J_WSRP ("opmnctl stopall; opmnctl startall")
Now you have a app server container that you can deploy your JSR-168/WSRP portlets to! Just deploy your ear files to this OC4J_WSRP.

Cant import iPhoto library. Locks up while "upgrading Library"

I have a new macbook air running OS X Mavericks. I tried to just copy the iphoto library from old mac to the pics library of new mac. I photo locks up while "upgrading library"
Tried to use migration assistant and it says I must first upgrade the OS of the old mac. My old mac cannot upgrade to mavericks, it is too old.
Suggestions?

Option 1
Back Up and try rebuild the library: hold down the command and option (or alt) keys while launching iPhoto. Use the resulting dialogue to rebuild. Choose to Repair Database. If that doesn't help, then try again, this time using Rebuild Database.
If that fails:
Option 2
Download iPhoto Library Manager and use its rebuild function. (In early versions of Library Manager it's the File -> Rebuild command. In later versions it's under the Library menu.)
This will create an entirely new library. It will then copy (or try to) your photos and all the associated metadata and versions to this new Library, and arrange it as close as it can to what you had in the damaged Library. It does this based on information it finds in the iPhoto sharing mechanism - but that means that things not shared won't be there, so no slideshows, books or calendars, for instance - but it should get all your events, albums and keywords, faces and places back.
Because this process creates an entirely new library and leaves your old one untouched, it is non-destructive, and if you're not happy with the results you can simply return to your old one.
Regards
TD

Error while upgrading 10g AS from 10.1.2.0.2 to 10.1.2.3

Hi All,
I am in process of doing 10g AS integration with 11.5.10.2.
As per documentation i have seen that 10g AS has to upgrade
My 10g AS version is 10.1.2.0.2
and my database version is 10.1.0.4.2
I have downloaded patch p5983622_10123_LINUX.zip
and first tried to upgrade infrastructure home
but while upgrading it says
oracle universal installer has detected that your database is version 10.1.0.4.2 before you can continue you must apply a required database patch set.
But in documentation i have seen
Supported Database Releases
The portal schema may be residing in an OracleAS Metadata Repository, or in a customer database. The database in which the portal schema resides must be one of the following supported releases:
Oracle Database 10g (10.1.0.4.2) or later
Please let me know what should i do now
Thanks in advance
Regards,
Bhanu Chander.

Hi ,
$ORACLE_HOME/j2ee/OC4J_Portal/application-deployments/portal/OC4J_Portal_default_island_1/application.log
09/09/24 06:24:21 portal: Max URL _debug value '1'.
09/09/24 06:36:33 portal: [module=PortalServletContextListener, thread=Shutdown] Portal Servlet Context Listener destroy started
09/09/24 06:36:33 portal: [module=PortalServletContextListener, thread=Shutdown] Repository Service destroy started
09/09/24 06:36:33 portal: [module=PortalServletContextListener, thread=Shutdown] Repository Service Config destroy started
09/09/24 06:36:33 portal: [module=PortalServletContextListener, thread=Shutdown] Repository Service Config destroy finished, 0 ms
09/09/24 06:36:34 portal: [module=PortalServletContextListener, thread=Shutdown] Repository Service destroy finished, 1003ms
09/09/24 06:36:34 portal: [module=PortalServletContextListener, thread=Shutdown] Portal Servlet Context Listener destroy finished, 1004ms
09/09/24 06:36:34 portal: Page Servlet destroy started at 1253788594974 millis
09/09/24 06:36:34 portal: Page Servlet destroy ended at 1253788594977 millis, duration was 3 millis
09/09/24 06:36:34 portal: [module=RepositoryServlet, thread=Shutdown] Repository Servlet destroy started
09/09/24 06:36:34 portal: RepositoryServlet: destroy
09/09/24 06:36:34 portal: [module=RepositoryServlet, thread=Shutdown] Repository Servlet destroy finished, 0ms
09/09/24 06:36:34 portal: [module=PortalServlet, thread=Shutdown] Portal Servlet destroy started
09/09/24 06:36:34 portal: PortalServlet: destroy
09/09/24 06:36:34 portal: [module=PortalServlet, thread=Shutdown] Portal Servlet destroy finished, 0ms
09/09/24 06:36:34 portal: Stopped
09/09/24 06:36:34 Stopped (Shutdown executed by jazn.com/admin from 127.0.0.1 (localhost.localdomain))
09/09/24 08:35:53 Started
09/09/24 08:36:13 portal: ServletLogger - Logging level: 2
09/09/24 08:36:13 portal: [module=PortalServletContextListener, thread=Orion Launcher] Initializing Portal Servlet Context Listener
09/09/24 08:36:13 portal: jsp: init
09/09/24 08:36:13 portal: Started
09/09/24 08:38:37 portal: PortalServlet: init
09/09/24 08:38:37 portal: ServletLogger - Logging level: 2
09/09/24 08:38:37 portal: [module=PortalServlet, thread=AJPRequestHandler-ApplicationServerThread-5] Initializing Servlet: PortalServlet
09/09/24 08:38:38 portal: RepositoryServlet: init
09/09/24 08:38:38 portal: ServletLogger - Logging level: 2
09/09/24 08:38:38 portal: [module=RepositoryServlet, thread=AJPRequestHandler-ApplicationServerThread-5] Initializing Servlet: RepositoryServlet
09/09/24 08:38:39 portal: page: init
09/09/24 08:38:39 portal: Cache: Cache is enabled.
09/09/24 08:38:39 portal: Pool: Initialized with the following pools : [oracle.webdb.pool.http.HTTPConnectionKey]
09/09/24 08:38:39 portal: Created mobileXML to HTML stylesheet object
09/09/24 08:38:39 portal: PPE version : 10.1.2.0.2 (11082005)
09/09/24 08:38:39 portal: Tuning parameter values : poolSize(Fetchers)=25[default=25] : minTimeout(MinTimeout)=5s[default=5s] : requesttime(DefaultTimeout)=15s[default=15s] : stall(MaxTimeout)=65s[default=65s] : queueTimeout(QueueTimeout)=10s[default=10s] maxParallelPortlets=20[default=20] maxParallelPagePortlets=10[default=10]
09/09/24 08:38:39 portal: Max URL _debug value '1'.
what do you see when you get the error on trying to login.
Same error
An error occurred while processing the request. Try refreshing your browser. If the problem persists contact the site administrator

R12 Database Version while upgrade

Similar Messages

Maybe you are looking for