Pre upgrade backup

Hi guys,
We are due to upgrade oracle rac, what are the diffrent options for backing up the linux OS and Oracle cluster/software binaries incase we need to restore to current version ?
Can I simply use cp to backup oracle home /grid home ? plus ocr&voting disk ? is that’s sufficient?

Hi
Look like you want to backup RAC binaries just in case you have to restore.
You have three or Two homes. Go into each home and use TAR command the out put file save on other mount point. If you to restore the binaries just UNTAR them in the corrosponding home.
If you like to backup database use data pump export or RMAN backup. I hope it will help you.
Thanks
MM

Similar Messages

  • CCX 7.0 pre-upgrade tool ERROR

    Dear ALL,
    I'm planning to upgrade my CCX 7.0 to the latest version,  I know that  I need to  take the backup  with pre-upgrade tool,
    But When  I enter  details of SFTP and  click to take a  backup  I'm getting this error:
    Cisco Unified CCX backup pre-check operation failed. Check the pre-upgrade tool log for more details.
    Please see below  the log file.
    May 4, 2015 2:12:07 PM com.cisco.ccx.w1.log.PUTLogger getLogger
    INFO: ############# Cisco Unified CCX W1 Pre-Upgrade Tool Logger #############
    May 4, 2015 2:12:07 PM com.cisco.ccx.w1.export.ui.PreUpgradeTool main
    INFO: Creating the Pre Upgrade Tool (1.0 Build 108)
    May 4, 2015 2:12:08 PM com.cisco.ccx.w1.export.ui.JHTMLEditorPane init
    WARNING: Pre-Upgrade Tool status colors C8D2DC, F3F3FF
    May 4, 2015 2:12:08 PM com.cisco.ccx.w1.export.ui.PreUpgradeTool initStatus
    INFO: Initializing the status windows
    May 4, 2015 2:12:29 PM com.cisco.ccx.w1.export.ui.WelcomeScreen jButton0ActionActionPerformed
    INFO: CCX Version is 7.0(1)_Build168
    May 4, 2015 2:15:49 PM com.cisco.ccx.w1.export.ui.SFTPScreen jButton0ActionActionPerformed
    INFO: Checking the SFTP connection. Server = 10.100.0.93 , UserName = cisco, Password = 0c52000a73
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.export.ui.ProgressScreen startBackup
    INFO: Starting the backup process ...
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.export.ui.ProgressScreen startBackup
    INFO: Initializing the Export manager thread.
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.export.ui.SFTPScreen jButton0ActionActionPerformed
    WARNING: Closing the SFTP connection.
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.export.ExportManager <init>
    INFO: W1 Pre-Upgrade Tool version is 1.0 Build 108
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.export.ExportManager <init>
    INFO: Instantiating the W1 Upgrade ExportManager.
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.export.ExportManager execute
    INFO: Starting the W1 Upgrade backup operation.
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.export.ExportManager execute
    INFO: ExportManager arguments are, {BackupLocation [Server = 10.100.0.93, Path = \, UserName = cisco, password = *******, Type = SFTP], StatusListener = com.cisco.ccx.w1.export.ui.W1StatusListener@d57bcb }
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.util.CCXUtil printRuntimeInfo
    INFO:
    ===========================
    Available Processors = 2
    JVM Max Memory = 493.06 MB
    JVM Total Memory = 106.94 MB
    JVM Free Memory = 83.61 MB
    ===========================
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.export.ExportManager init
    INFO: W1 Config contents [ ConfigMap : {$$Backup Data Type=W1 Pre Upgrade Backup, JRE Version=1.6.0_13, PUT Version=1.0 Build 108, OS Version=Windows 2003,x86,5.2, Backup Start Time=Mon May 04 14:15:57 AZST 2015, User Name=Administrator}
     ParamMap : {}
     AppProperty : {com.cisco.ccx.w1.proxy.enabled=true, w1.stage.alarm=config\alarm, w1.put.instance.nwerr.skip=true, w1.stage.logs=logs, w1.stage.recordings=recordings, com.cisco.ccx.w1.put.retry=5, com.cisco.ccx.w1.put.colors=C8D2DC,F3F3FF, com.cisco.ccx.config.mgr.args=, w1.put.instance.port=13403, com.cisco.ccx.w1.put.lnf=com.sun.java.swing.plaf.nimbus.NimbusLookAndFeel, w1.stage.jtrace=config\jtapi, w1.stage.database=db, w1.stage.config=config, com.cisco.ccx.w1.config.properties=CustomFileClasspath.properties,currency.properties,SubsystemRmCm.properties,TTSProvider.properties,CustomStep.properties,CustomSubsystem.properties,SubsystemEDBS.properties,locale.properties,application.MIVR.properties,system.properties, com.cisco.ccx.w1.cl.timeout=120, com.cisco.ccx.w1.stage.dir=C:\W1-STI, w1.stage.license=7xLicense, w1.stage.calabrio=cl}
     Backup dir : C:\W1-STI ]
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.export.ExportManager isDefaultLocale
    INFO: checking if the locale is set to the default locale en_US)
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.export.ExportManager isDefaultLocale
    INFO: The current locale is ...en_US
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.export.ExportManager isCCXVersionSupported
    INFO: CCX version  = 7.0(1)_Build168
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.cvd.CVDCommunicator <init>
    INFO: CVDCommunicator default constructor.
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.cvd.CVDCommunicator getCVDPort
    INFO: Default CVD port set as 994
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.cvd.CVDCommunicator getCVDPort
    INFO: Querying  WIN registry on localhost to get the CVD Master listener port.
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.cvd.CVDCommunicator getCVDPort
    INFO: CVD Master listener port string returned from registry = 994
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.cvd.CVDCommunicator getCVDPort
    INFO: Returning CVD Master listener port : 994
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.cvd.CVDCommunicator <init>
    INFO: ccxHost = /127.0.0.1 port = 994
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.cvd.CVDCommunicator openCVDSession
    INFO: Getting the socket input and output stream.
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.cvd.CVDCommunicator openCVDSession
    INFO: Sending a CVD Open Session request.
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.cvd.CVDCommunicator sendOpenSessionReq
    INFO: Sending {Req = OPEN_REQ, versionNbr = 1 , invokeID = 123 }
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.cvd.CVDCommunicator openCVDSession
    INFO: Waiting for a CVD Open Session response.
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.cvd.CVDCommunicator processResponse
    INFO: Response header is :  { Msg Len : 4 , Msg Type : OPEN_CONF }
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.cvd.CVDCommunicator processOpenSessionResponse
    INFO: Invoke ID : 123
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.cvd.CVDCommunicator openCVDSession
    INFO: Got the CVD Open Session response.
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.export.ExportManager initCVDCommunicator
    INFO: Initialized the CVDCommunicator
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.cvd.CVDCommunicator sendSvcSnapshotReq
    INFO: Sending {Req = ENABLE_SNAPSHOT_REQ,  service = CRS Cluster View Daemon }
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.cvd.CVDCommunicator processResponse
    INFO: Response header is :  { Msg Len : 42 , Msg Type : ENABLE_SNAPSHOT_CONF }
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.cvd.CVDCommunicator processSnapshotResponse
    INFO: Requested service : CRS Cluster View Daemon, service in response : CRS Cluster View Daemon
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.cvd.CVDCommunicator processSnapshotResponse
    INFO: Total service count : 2
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.cvd.CVDCommunicator processSnapshotResponse
    INFO: IP Address : 172.30.30.4, state : 2
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.cvd.CVDCommunicator processSnapshotResponse
    INFO: IP Address : 172.30.30.5, state : 0
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.cvd.CVDCommunicator sendSvcSnapshotReq
    INFO: Sending {Req = ENABLE_SNAPSHOT_REQ,  service = CRS Engine }
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.cvd.CVDCommunicator processResponse
    INFO: Response header is :  { Msg Len : 29 , Msg Type : ENABLE_SNAPSHOT_CONF }
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.cvd.CVDCommunicator processSnapshotResponse
    INFO: Requested service : CRS Engine, service in response : CRS Engine
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.cvd.CVDCommunicator processSnapshotResponse
    INFO: Total service count : 2
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.cvd.CVDCommunicator processSnapshotResponse
    INFO: IP Address : 172.30.30.4, state : 6
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.cvd.CVDCommunicator processSnapshotResponse
    INFO: IP Address : 172.30.30.5, state : 0
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.cvd.CVDCommunicator sendSvcSnapshotReq
    INFO: Sending {Req = ENABLE_SNAPSHOT_REQ,  service = Cisco Desktop Recording Service }
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.cvd.CVDCommunicator processResponse
    INFO: Response header is :  { Msg Len : 50 , Msg Type : ENABLE_SNAPSHOT_CONF }
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.cvd.CVDCommunicator processSnapshotResponse
    INFO: Requested service : Cisco Desktop Recording Service, service in response : Cisco Desktop Recording Service
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.cvd.CVDCommunicator processSnapshotResponse
    INFO: Total service count : 2
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.cvd.CVDCommunicator processSnapshotResponse
    INFO: IP Address : 172.30.30.4, state : 2
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.cvd.CVDCommunicator processSnapshotResponse
    INFO: IP Address : 172.30.30.5, state : 0
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.cvd.CVDCommunicator sendSvcSnapshotReq
    INFO: Sending {Req = ENABLE_SNAPSHOT_REQ,  service = Cisco Desktop VoIP Monitor Service }
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.cvd.CVDCommunicator processResponse
    INFO: Response header is :  { Msg Len : 53 , Msg Type : ENABLE_SNAPSHOT_CONF }
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.cvd.CVDCommunicator processSnapshotResponse
    INFO: Requested service : Cisco Desktop VoIP Monitor Service, service in response : Cisco Desktop VoIP Monitor Service
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.cvd.CVDCommunicator processSnapshotResponse
    INFO: Total service count : 2
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.cvd.CVDCommunicator processSnapshotResponse
    INFO: IP Address : 172.30.30.4, state : 2
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.cvd.CVDCommunicator processSnapshotResponse
    INFO: IP Address : 172.30.30.5, state : 0
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.export.ExportManager checkMaster
    INFO: Querying engine master and DB  publisher node.
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.cvd.CVDCommunicator sendRegMasterListener
    INFO: Sending {Req = REG_MASTER_LISTENER, masterName = CRS Engine }
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.cvd.CVDCommunicator processResponse
    INFO: Response header is :  { Msg Len : 16 , Msg Type : REG_MASTER_CONF }
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.cvd.CVDCommunicator processMasterResponse
    INFO: Master service name in the response : CRS Engine
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.cvd.CVDCommunicator processMasterResponse
    INFO: Master IP address in the response : 172.30.30.4
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.cvd.CVDCommunicator sendRegMasterListener
    INFO: Sending {Req = REG_MASTER_LISTENER, masterName = CRS SQL Server - Historical }
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.cvd.CVDCommunicator processResponse
    INFO: Response header is :  { Msg Len : 33 , Msg Type : REG_MASTER_CONF }
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.cvd.CVDCommunicator processMasterResponse
    INFO: Master service name in the response : CRS SQL Server - Historical
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.cvd.CVDCommunicator processMasterResponse
    INFO: Master IP address in the response : 172.30.30.4
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.export.ExportManager checkMaster
    INFO: Engine master node = 172.30.30.4, DB publisher = 172.30.30.4
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.export.ExportManager checkLicense
    INFO: Validating the license info.
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.cvd.CVDCommunicator sendChkoutLicenseRequest
    INFO: Sending {Req = CHECKOUT_LICENSE_REQ,  license = IVR_ENHANCED }
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.cvd.CVDCommunicator processResponse
    INFO: Response header is :  { Msg Len : 18 , Msg Type : CHECKOUT_LICENSE_CONF }
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.cvd.CVDCommunicator processLicChkoutResponse
    INFO: Requested license : IVR_ENHANCED, License in response : IVR_ENHANCED
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.cvd.CVDCommunicator processLicChkoutResponse
    INFO: License checkout : true
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.cvd.CVDCommunicator sendLicenseRequest
    INFO: Sending {Req = GET_LICENSE_REQ,  license = PRE_SEAT }
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.cvd.CVDCommunicator processResponse
    INFO: Response header is :  { Msg Len : 14 , Msg Type : GET_LICENSE_CONF }
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.cvd.CVDCommunicator processLicenseResponse
    INFO: Requested license : PRE_SEAT, License in response : PRE_SEAT
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.cvd.CVDCommunicator processLicenseResponse
    INFO: License Count : 5
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.cvd.CVDCommunicator sendChkoutLicenseRequest
    INFO: Sending {Req = CHECKOUT_LICENSE_REQ,  license = WARM_STANDBY }
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.cvd.CVDCommunicator processResponse
    INFO: Response header is :  { Msg Len : 18 , Msg Type : CHECKOUT_LICENSE_CONF }
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.cvd.CVDCommunicator processLicChkoutResponse
    INFO: Requested license : WARM_STANDBY, License in response : WARM_STANDBY
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.cvd.CVDCommunicator processLicChkoutResponse
    INFO: License checkout : true
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.cvd.CVDCommunicator sendLicenseRequest
    INFO: Sending {Req = GET_LICENSE_REQ,  license = IVR_PORTS }
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.cvd.CVDCommunicator processResponse
    INFO: Response header is :  { Msg Len : 15 , Msg Type : GET_LICENSE_CONF }
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.cvd.CVDCommunicator processLicenseResponse
    INFO: Requested license : IVR_PORTS, License in response : IVR_PORTS
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.cvd.CVDCommunicator processLicenseResponse
    INFO: License Count : 10
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.export.ExportManager checkLicense
    INFO: License Package = Cisco Unified CCX Premium, SeatCount = 5, HA = true, IVR Ports = 10
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.export.ExportManager checkLicense
    INFO: ## License package is Express
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.cvd.CVDCommunicator close
    INFO: Closing the CVD connection.
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.export.ExportManager checkProxy
    INFO: Checking the proxy configurations.
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.util.proxy.ProxyUtil isManualProxyEnabled
    INFO: Proxy Enable Reg Value : dword:00000000
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.util.proxy.ProxyUtil isManualProxyEnabled
    INFO: Manual proxy NOT enabled.
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.util.proxy.ProxyUtil isAutoProxyEnabled
    INFO: Proxy Auto Config URL : null
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.util.proxy.ProxyUtil isAutoProxyEnabled
    INFO: Proxy Auto Config NOT enabled.
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.util.proxy.ProxyUtil isJavaProxyEnabled
    INFO: Checking the Java proxy settings.
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.util.proxy.ProxyUtil isJavaProxyEnabled
    INFO: Querying applicable proxies for the protocol => "http"
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.util.proxy.ProxyUtil isJavaProxyEnabled
    INFO: Applicable Proxies : [DIRECT]
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.util.proxy.ProxyUtil isJavaProxyEnabled
    INFO: Querying applicable proxies for the protocol => "https"
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.util.proxy.ProxyUtil isJavaProxyEnabled
    INFO: Applicable Proxies : [DIRECT]
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.util.proxy.ProxyUtil isJavaProxyEnabled
    INFO: Querying applicable proxies for the protocol => "ftp"
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.util.proxy.ProxyUtil isJavaProxyEnabled
    INFO: Applicable Proxies : [DIRECT]
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.util.proxy.ProxyUtil isJavaProxyEnabled
    INFO: Querying applicable proxies for the protocol => "gopher"
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.util.proxy.ProxyUtil isJavaProxyEnabled
    INFO: Applicable Proxies : [DIRECT]
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.util.proxy.ProxyUtil isJavaProxyEnabled
    INFO: Querying applicable proxies for the protocol => "socket"
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.util.proxy.ProxyUtil isJavaProxyEnabled
    INFO: Applicable Proxies : [DIRECT]
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.util.proxy.ProxyUtil isJavaProxyEnabled
    INFO: Java Proxy NOT enabled.
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.config.mgr.ConfigManagerStarter <clinit>
    INFO: Cisco Unified CCX root directory : c:\progra~1\wfavvid
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.config.mgr.ConfigManagerStarter isMMStarted
    INFO: Manager Manager is NOT started
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.config.mgr.ConfigManagerStarter initMM
    INFO: Creating the Windows URL classloader params
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.config.mgr.ConfigManagerStarter createParams
    INFO: Raw URLClassloaderParams : "Editor Class Loader";{0}\CiscoManagerManagerImpl.jar;com.cisco.manager.impl.ManagerManagerImpl;-property;{1};{2};{3};{4};-rootdir;{5};com.cisco.ccx.w1.config.mgr.MMInitLock
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.config.mgr.ConfigManagerStarter initMM
    INFO: URLClassloaderParams : "Editor Class Loader", c:\progra~1\wfavvid\lib\CiscoManagerManagerImpl.jar, com.cisco.manager.impl.ManagerManagerImpl, -property, application.MCET.properties, -nokeepalive, -rootdir, c:\progra~1\wfavvid, com.cisco.ccx.w1.config.mgr.MMInitLock
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.config.mgr.ConfigManagerStarter initMM
    INFO: Redirecting the ManagerManagerImpl output
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.config.mgr.ConfigManagerStarter initMM
    INFO: Invoking the ManagerManagerImpl using the URLClassloader
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.config.mgr.URLClassLoader main
    INFO: Invoking the URLClassLoader
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.config.mgr.URLClassLoader convertToURL
    INFO: *** Adding classpath: c:\progra~1\wfavvid\lib\CiscoManagerManagerImpl.jar, URL = file:/c:/progra~1/wfavvid/lib/CiscoManagerManagerImpl.jar
    May 4, 2015 2:15:58 PM com.cisco.ccx.w1.config.mgr.ConfigManagerStarter initMM
    INFO: ManagerManagerImpl initialization completed and waiting for the MMInitLock(Startable class to get invoked)
    May 4, 2015 2:15:59 PM com.cisco.ccx.w1.config.mgr.MMInitLock start
    INFO: Inside the startable class
    May 4, 2015 2:15:59 PM com.cisco.ccx.w1.config.mgr.MMInitLock start
    INFO: Notifying the object waiting for the mutex
    May 4, 2015 2:15:59 PM com.cisco.ccx.w1.config.mgr.ConfigManagerStarter initMM
    INFO: Config framework started completely.
    May 4, 2015 2:15:59 PM com.cisco.ccx.w1.config.mgr.ConfigManagerStarter initMM
    INFO: Restoring the Outputstream if -redirect is enabled
    May 4, 2015 2:15:59 PM com.cisco.ccx.w1.export.cl.CLMigration getAllNodeIPs
    INFO: Cluster IP addresses are, 172.30.30.5, 172.30.30.4
    May 4, 2015 2:16:00 PM com.cisco.ccx.w1.export.ExportManager startConfigManager
    INFO: CCX Node with IP address 172.30.30.5 is reachable.
    May 4, 2015 2:16:01 PM com.cisco.ccx.w1.export.ExportManager startConfigManager
    INFO: CCX Node with IP address 172.30.30.4 is reachable.
    May 4, 2015 2:16:01 PM com.cisco.ccx.w1.export.ExportManager startConfigManager
    INFO: Getting the node config for UCCX1
    May 4, 2015 2:16:01 PM com.cisco.ccx.w1.export.ExportManager startConfigManager
    INFO: Local node config is NodeConfig[schema=NodeConfig,time=Mon Nov 09 12:55:40 AZT 2009,recordId=-668476853,desc=,node id=1,computer name=UCCX1,ip addresses=172.30.30.4,model=7816I02,nodeGuid={BDF658EF-26F2-4871-8FE4-C508A8AD387E},osArchitecture=X86-based PC,osName=Microsoft Windows Server 2003,osVersion=502,vendor=IBM,installtime=Mon Nov 09 12:55:03 AZT 2009,upgrade time=Mon Nov 09 12:55:03 AZT 2009,ccm colocated=false,deployment type=1,harddisk size=236472,install path=C:\Program Files\wfavvid\]
    May 4, 2015 2:16:01 PM com.cisco.ccx.w1.export.ExportManager startConfigManager
    INFO: Getting all engine node ids.
    May 4, 2015 2:16:01 PM com.cisco.ccx.w1.export.ExportManager startConfigManager
    INFO: Engine node ids = 2,1
    May 4, 2015 2:16:01 PM com.cisco.ccx.w1.db.util.DatabaseUtil getInstance
    INFO: Creating the DB Util instance.
    May 4, 2015 2:16:01 PM com.cisco.ccx.w1.db.util.DatabaseUtil <init>
    INFO: Loading the net.sourceforge.jtds.jdbc.Driver
    May 4, 2015 2:16:01 PM com.cisco.ccx.w1.db.util.DatabaseUtil <init>
    INFO: DB Publisher IP is 172.30.30.4
    May 4, 2015 2:16:01 PM com.cisco.ccx.w1.db.util.DatabaseUtil <init>
    INFO: DB CRA Url =  jdbc:jtds:sqlserver://172.30.30.4:4433/db_cra
    May 4, 2015 2:16:01 PM com.cisco.ccx.w1.db.util.DatabaseUtil <init>
    INFO: DB CRA Repository Url =  jdbc:jtds:sqlserver://172.30.30.4:4433/db_cra_repository
    May 4, 2015 2:16:01 PM com.cisco.ccx.w1.db.util.DatabaseUtil <init>
    INFO: FCRasSvr Url =  jdbc:jtds:sqlserver://172.30.30.4:4433/FCRasSvr
    May 4, 2015 2:16:01 PM com.cisco.ccx.w1.db.util.DatabaseUtil getConnection
    INFO: Getting connection for jdbc:jtds:sqlserver://172.30.30.4:4433/db_cra
    May 4, 2015 2:16:01 PM com.cisco.ccx.w1.db.util.DatabaseUtil getConnection
    INFO: Obtaining new Connection.
    May 4, 2015 2:16:01 PM com.cisco.ccx.w1.db.util.DatabaseUtil getDbSpaceUsed
    INFO: DB Spaced used for db_cra is 479117312 bytes
    May 4, 2015 2:16:01 PM com.cisco.ccx.w1.export.ExportManager checkSpace
    INFO: Max allowed DB space=10.00 GB, Used db_cra space=456.92 MB
    May 4, 2015 2:16:01 PM com.cisco.ccx.w1.db.util.DatabaseUtil getConnection
    INFO: Getting connection for jdbc:jtds:sqlserver://172.30.30.4:4433/db_cra_repository
    May 4, 2015 2:16:01 PM com.cisco.ccx.w1.db.util.DatabaseUtil getConnection
    INFO: Obtaining new Connection.
    May 4, 2015 2:16:01 PM com.cisco.ccx.w1.db.util.DatabaseUtil getDbSpaceUsed
    INFO: DB Spaced used for db_cra_repository is 9175040 bytes
    May 4, 2015 2:16:01 PM com.cisco.ccx.w1.db.util.DatabaseUtil getConnection
    INFO: Getting connection for jdbc:jtds:sqlserver://172.30.30.4:4433/FCRasSvr
    May 4, 2015 2:16:01 PM com.cisco.ccx.w1.db.util.DatabaseUtil getConnection
    INFO: Obtaining new Connection.
    May 4, 2015 2:16:01 PM com.cisco.ccx.w1.db.util.DatabaseUtil getDbSpaceUsed
    INFO: DB Spaced used for FCRasSvr is 6938624 bytes
    May 4, 2015 2:16:01 PM com.cisco.ccx.w1.export.ExportManager checkSpace
    INFO: Estimating the recording file size.
    May 4, 2015 2:16:01 PM com.cisco.ccx.w1.export.cl.CLMigration getAllNodeIPs
    INFO: Cluster IP addresses are, 172.30.30.4, 172.30.30.5
    May 4, 2015 2:16:01 PM com.cisco.ccx.w1.export.cl.CLMigration getRecordingFolder
    INFO: Recording file location for the node 172.30.30.4 is C:\Program Files\Cisco\Desktop_Audio
    May 4, 2015 2:16:01 PM com.cisco.ccx.w1.export.cl.CLMigration getRecordingFolder
    INFO: Recording folder UNC path for node 172.30.30.4 is \\172.30.30.4\C$\Program Files\Cisco\Desktop_Audio
    May 4, 2015 2:16:01 PM com.cisco.ccx.w1.export.ExportManager getRecSpace
    INFO: Recording folder (*.Raw) size for IP 172.30.30.4 is 0.00 Bytes
    May 4, 2015 2:16:43 PM com.cisco.ccx.w1.export.ExportManager preCheck
    SEVERE: Error while doing Cisco Unified CCX backup pre-check
    com.cisco.lang.IllegalArgumentException: errCode=-1; nested exception is:
        com.ice.jni.registry.RegistryException: Registry API Error 53, '' - 'RegConnectRegistry()'
        at com.cisco.util.RegistryProperties.<init>(RegistryProperties.java:474)
        at com.cisco.util.RegistryProperties.<init>(RegistryProperties.java:408)
        at com.cisco.ccx.w1.export.cl.CLConfigUtil.getRegHandle(CLConfigUtil.java:300)
        at com.cisco.ccx.w1.export.cl.CLConfigUtil.getRecordingsLocation0(CLConfigUtil.java:221)
        at com.cisco.ccx.w1.export.cl.CLConfigUtil.getRecordingsLocation(CLConfigUtil.java:183)
        at com.cisco.ccx.w1.export.cl.CLMigration.getRecordingFolder(CLMigration.java:493)
        at com.cisco.ccx.w1.export.ExportManager.getRecSpace(ExportManager.java:926)
        at com.cisco.ccx.w1.export.ExportManager.checkSpace(ExportManager.java:995)
        at com.cisco.ccx.w1.export.ExportManager.preCheck(ExportManager.java:593)
        at com.cisco.ccx.w1.export.ExportManager.process(ExportManager.java:371)
        at com.cisco.ccx.w1.export.ExportManager.execute(ExportManager.java:263)
        at com.cisco.ccx.w1.export.ui.ProgressScreen$1.run(ProgressScreen.java:80)
        nested stack trace is:
        com.ice.jni.registry.RegistryException: Registry API Error 53, '' - 'RegConnectRegistry()'
        at com.ice.jni.registry.RegistryKey.connectRegistry(Native Method)
        at com.cisco.util.RegistryProperties.<init>(RegistryProperties.java:441)
        at com.cisco.util.RegistryProperties.<init>(RegistryProperties.java:408)
        at com.cisco.ccx.w1.export.cl.CLConfigUtil.getRegHandle(CLConfigUtil.java:300)
        at com.cisco.ccx.w1.export.cl.CLConfigUtil.getRecordingsLocation0(CLConfigUtil.java:221)
        at com.cisco.ccx.w1.export.cl.CLConfigUtil.getRecordingsLocation(CLConfigUtil.java:183)
        at com.cisco.ccx.w1.export.cl.CLMigration.getRecordingFolder(CLMigration.java:493)
        at com.cisco.ccx.w1.export.ExportManager.getRecSpace(ExportManager.java:926)
        at com.cisco.ccx.w1.export.ExportManager.checkSpace(ExportManager.java:995)
        at com.cisco.ccx.w1.export.ExportManager.preCheck(ExportManager.java:593)
        at com.cisco.ccx.w1.export.ExportManager.process(ExportManager.java:371)
        at com.cisco.ccx.w1.export.ExportManager.execute(ExportManager.java:263)
        at com.cisco.ccx.w1.export.ui.ProgressScreen$1.run(ProgressScreen.java:80)
    May 4, 2015 2:16:50 PM com.cisco.ccx.w1.export.ExportManager destroy
    INFO: Cisco Unified CCX Backup destroy called.
    May 4, 2015 2:16:50 PM com.cisco.ccx.w1.export.ExportManager destroy
    INFO: Final W1 Config contents [ ConfigMap : {License Seat Count=5, Unified CCX Engine Master=172.30.30.4, Unified CCX Engine Count=2, PUT Run On=172.30.30.4, Engine Node IDs=2,1, PUT Version=1.0 Build 108, OS Version=Windows 2003,x86,5.2, Node ID=1, User Name=Administrator, License Package Type=Cisco Unified Express, Unified CCX Rec Nodes=172.30.30.4, 172.30.30.5, IVR Port Count=10, License Package=Cisco Unified CCX Premium, $$Backup Data Type=W1 Pre Upgrade Backup, JRE Version=1.6.0_13, Unified CCX Mon Nodes=172.30.30.4, 172.30.30.5, Unified CCX Nodes=172.30.30.4, 172.30.30.5, Backup Start Time=Mon May 04 14:15:57 AZST 2015, Host Name=UCCX1, Unified CCX DB Publisher=172.30.30.4}
     ParamMap : {Unified CCX Engine Count=2, node.id=1, IVR Port Count=10}
     AppProperty : {com.cisco.ccx.w1.proxy.enabled=true, w1.stage.alarm=config\alarm, w1.put.instance.nwerr.skip=true, w1.stage.logs=logs, w1.stage.recordings=recordings, com.cisco.ccx.w1.put.retry=5, com.cisco.ccx.w1.put.colors=C8D2DC,F3F3FF, com.cisco.ccx.config.mgr.args=, w1.put.instance.port=13403, com.cisco.ccx.w1.put.lnf=com.sun.java.swing.plaf.nimbus.NimbusLookAndFeel, w1.stage.jtrace=config\jtapi, w1.stage.database=db, w1.stage.config=config, com.cisco.ccx.w1.config.properties=CustomFileClasspath.properties,currency.properties,SubsystemRmCm.properties,TTSProvider.properties,CustomStep.properties,CustomSubsystem.properties,SubsystemEDBS.properties,locale.properties,application.MIVR.properties,system.properties, com.cisco.ccx.w1.cl.timeout=120, com.cisco.ccx.w1.stage.dir=C:\W1-STI, w1.stage.license=7xLicense, w1.stage.calabrio=cl}
     Backup dir : C:\W1-STI ]
    May 4, 2015 2:16:50 PM com.cisco.ccx.w1.export.ExportManager execute
    SEVERE: Cisco Unified CCX Backup operation failed. ProcessResult = false
    May 4, 2015 2:16:50 PM com.cisco.ccx.w1.export.ui.JHTMLEditorPane saveStatus
    INFO: Saving the PUT backup status and logs.
    May 4, 2015 2:16:50 PM com.cisco.ccx.w1.export.ui.JHTMLEditorPane createZip
    INFO: Getting the PUT log files from C:\
    May 4, 2015 2:16:50 PM com.cisco.ccx.w1.export.ui.JHTMLEditorPane createZip
    INFO: Creating the log archive file C:\PUTLog04-May-15#14-16.zip
    May 4, 2015 2:16:50 PM com.cisco.ccx.w1.export.ui.JHTMLEditorPane saveStatus
    INFO: PUT logs backup completed.
    May 4, 2015 2:16:50 PM com.cisco.ccx.w1.util.CCXUtil printRuntimeInfo
    INFO:
    ===========================
    Available Processors = 2
    JVM Max Memory = 493.06 MB
    JVM Total Memory = 118.88 MB
    JVM Free Memory = 90.53 MB
    ===========================

    The primary reason for this error is when a codec is not installed on the box that your running Windows Media Player from (that is the common knowledge part)...a possible reason for this could be that some wav files are being saved in different formats than others. A quick check to see if there are different CTI port groups configured to use different codec would prove that out. Also...can you play the files on another computer or in a different player like VLC?
    Peace,
    Michael Clendening

  • UCCX 5.0 - 8.0 using pre-upgrade tool

    Hi,
    We're upgrading from 5.0(2) to 8.0. We've used the Pre-Upgrade Tool to create a TAR file on the production UCCX. From the replacement server we've selected "Upgrade from a previous UCCX release". The Pre-Upgrade Tool ran without issue and the log file shows no errors.
    The status message shows: "Enter a valid backup file"
    We know the sftp server is setup correctly and the user credentials are correct.
    Any feedback welcome.Many thanks.

    The Pre-Upgrade Tool also have the option to verify the backup file. Try running the verification and see if it works:
    (page 16 - Upgrade guide)
    http://www.cisco.com/en/US/docs/voice_ip_comm/cust_contact/contact_center/crs/express_8_0/installation/guide/uccx801ig.pdf
    Also what are the exact UCCX versions 5.0(2) SR? and going to 8.0(1) or 8.0(2)? there is one upgrade tool for 8.0(1) and another for 8.0(2), make sure you are running the right one.
    Pablo

  • How to run Pre-Upgrade Check without upgrading License Server

    Hi
    How can I run the 8.8 Pre-Upgrade Check without upgrading to the 8.8 license server?
    The Wizard forces me to upgrade it and if I upgrade it, the current 2007 does not run anymore. I want to check my DB's with the Check before upgrading any components and 2007 needs to stay alive.
    Thanks
    Franz

    Hi Franz,
    I would suggest you to check your DBu2019s in your test environment. Please take a backup of all DBu2019s from your live environment and restore them in your test environment once you will have enough free space.
    Please always test the database upgrade in the test environment before doing it in the production environment.
    For more information regarding Business One installation and upgrades on 8.8 version please refer to the Administrator's Guide 8.8, which can be found on the Documentation Resource Centre on the Portal. http://service.sap.com/smb/sbo/documentation  ->  Documentation Resource Center for Release 8.8 
    See chapters: 3.Installing SAP Business One and 5.Upgrading SAP Business One
    Regards,
    Ladislav Meszaros
    SAP Business One Forum Team

  • I am trying to update my iTunes to 10.5.1 so that I can upgrade my 3GS phone but am getting the following error message when trying to install the itunes:Install step failed: Run pre upgrade script for apple mobile device support. Contact software manufac

    I am trying to update my iTunes to 10.5.1 so that I can upgrade my 3GS phone but am getting the following error message when trying to install the itunes: Install step failed: Run pre upgrade script for apple mobile device support. Contact software manufacturer for assistance. I am on a MacBook pro running 10.5.8 OS. Has anyone seen this before and how can I get it resolved.
    Thanks for your help in advance....

    Did you ever figure out the problem? "Contact Software Manufacturer"?? That sounds ominous... I've got the same issue and I'm pretty durn aggravated right about now....
    Thanks!

  • SLA Pre- upgrade programs and process and SLA Post upgrade

    Hi Guys
    Can anybody please let me know what are the SLA Pre- upgrade programs and process we have to run and SLA Post upgrade process and programs.
    Thanks
    Ajeesh

    Pl post details of OS and EBS versions. Pl see if MOS Doc 604893.1 (R12: FAQ for the SLA Upgrade: SLA Pre-Upgrade, Post-Upgrade, and Hot Patch) can help
    HTH
    Srini

  • Recovering file pre-migration backup

    I am trying to recover a Themes file from inside my old iWeb application on my pre-migration MacBook Pro backup, however, in Time Machine the all pre-migration backups for the MacBook pro are shown on the right, but are grayed out and not accessible. Only backups of the new computer since the migration are available.
    Also, after migrating from the old MacBook Pro to new iMac, I chose the Time Machine option to continue the original Time Capsule backup from the previous MacBook Pro. I have tried Migration Assistant, but it does not let me just access the old backups.
    How do I access the previous MacBook Pro backups on my Time Capsule from my new computer?

    Chuck, forgive the spelling in the previous post. It was from my iPhone while I was out.
    chuckburr wrote:
    Good question. I send the Migration Assistant to migrate from my old MacBook Pro to the new iMac via Ethernet.
    If you are actually logged into the very same account that existed on your old Mac, then I'm not sure why you can't get at the old backups. That scenario has worked just fine for me in the past.
    TM started on the new iMac and asked me if I wanted to start a new backup or continue the old one. I figured that since I had just migrated the entire user and places to the new computer I should continue with the same backup. I did not anticipate that it would not let me into old backups.
    That is a perfectly reasonable assumption, particularly now that Mac OSX permits you to do that - which was not the case before Snow Leopard. As I said, there is some reason the system thinks that is another users data and won't let you at it (Am I correct in assuming that the MBP is now gone?).
    The Migration moved everything except fine stuff such as custom Themes within iWeb. One application with in the iLife suite may have needed to be reloaded so I reloaded the quite which may have been the cause of writing over the old iWeb, so now I am just trying to go back and get the theme out of the old iWeb so to speak.
    Do you have any other accounts setup on the new Mac? Have you tried logging into one of them, mounting the TM backup disk image and then "Browse Other Backup Disk..."?

  • Oracle Upgrade --  Pre-Upgrade 10.2.0.4 to 11.2.0.1

    Hello,
    I want to do an Oracle Upgrade to version 11.2g!
    At this point I did some things (in Windows Server 2003 X64):
    1-) Install Oracle 10.2.0.1 (DVD Media);
    2-) Installation of Oracle patchset 10.2.0.4 (note 871735);
    3-) Installation of interim / last generics patch (note 1137346);
    4-) Installation of SAP ECC 6.0 SR3 by SAPInst
    5-) After SAP installation I did all the corrections in Oracle parameters as it mentioned in note 830576.
    As you see above, all the SAP system was well installed!
    But now I want to do the Oracle Upgrade process to the last version, Oracle DB 11.2g  (11.2.0.1)... and so I´m following the Upgrade guide "Upgrade to Oracle Database 11g Release 2 (11.2) Windows.pdf" with some SAP notes for Upgrade process.
    So I´m at this point in planning chapter where is recommended to check so things in actual database, one of this checks are running some SQL-scripts to perform an Oracle database upgrade with DBUA to release 11.2 (as mentioned in note 1431793 - Oracle 11.2.0: Upgrade Scripts)
    I ran two Pre-Scripts, the @pre_upgrade_status.sql and @pre_upgrade_tasks.sql but both outputs showed some warnings and they are worrying me... so what I ask to you is some kind of help in analyse of them and tell me if this issues are relevant for the upgrading process and if so, what you recommend me to do to correct their!
    Next I will post here this two log scripts... they are long!!!

    PRE_UPGRADE_TASKS.log:
    SQL> @pre_upgrade_tasks.sql
    PRE-UPGRADE Tasks: === START ===
    2010-08-05 18:24:13                                                                               
    Recompiling invalid objects
    This reduces the number of invalid objects as much as possible.
    COMP_TIMESTAMP UTLRP_BGN  2010-08-05 18:24:13                                                      
    DOC>   The following PL/SQL block invokes UTL_RECOMP to recompile invalid
    DOC>   objects in the database. Recompilation time is proportional to the
    DOC>   number of invalid objects in the database, so this command may take
    DOC>   a long time to execute on a database with a large number of invalid
    DOC>   objects.
    DOC>
    DOC>   Use the following queries to track recompilation progress:
    DOC>
    DOC>   1. Query returning the number of invalid objects remaining. This
    DOC>       number should decrease with time.
    DOC>          SELECT COUNT(*) FROM obj$ WHERE status IN (4, 5, 6);
    DOC>
    DOC>   2. Query returning the number of objects compiled so far. This number
    DOC>       should increase with time.
    DOC>          SELECT COUNT(*) FROM UTL_RECOMP_COMPILED;
    DOC>
    DOC>   This script automatically chooses serial or parallel recompilation
    DOC>   based on the number of CPUs available (parameter cpu_count) multiplied
    DOC>   by the number of threads per CPU (parameter parallel_threads_per_cpu).
    DOC>   On RAC, this number is added across all RAC nodes.
    DOC>
    DOC>   UTL_RECOMP uses DBMS_SCHEDULER to create jobs for parallel
    DOC>   recompilation. Jobs are created without instance affinity so that they
    DOC>   can migrate across RAC nodes. Use the following queries to verify
    DOC>   whether UTL_RECOMP jobs are being created and run correctly:
    DOC>
    DOC>   1. Query showing jobs created by UTL_RECOMP
    DOC>          SELECT job_name FROM dba_scheduler_jobs
    DOC>          WHERE job_name like 'UTL_RECOMP_SLAVE_%';
    DOC>
    DOC>   2. Query showing UTL_RECOMP jobs that are running
    DOC>          SELECT job_name FROM dba_scheduler_running_jobs
    DOC>          WHERE job_name like 'UTL_RECOMP_SLAVE_%';
    DOC>#
    COMP_TIMESTAMP UTLRP_END  2010-08-05 18:24:15                                                      
    DOC> The following query reports the number of objects that have compiled
    DOC> with errors (objects that compile with errors have status set to 3 in
    DOC> obj$). If the number is higher than expected, please examine the error
    DOC> messages reported with each object (using SHOW ERRORS) to see if they
    DOC> point to system misconfiguration or resource constraints that must be
    DOC> fixed before attempting to recompile these objects.
    DOC>#
                      0                                                                               
    DOC> The following query reports the number of errors caught during
    DOC> recompilation. If this number is non-zero, please query the error
    DOC> messages in the table UTL_RECOMP_ERRORS to see if any of these errors
    DOC> are due to misconfiguration or resource constraints that must be
    DOC> fixed before objects can compile successfully.
    DOC>#
                              0                                                                        
    Purging Recyclebin
    This reduces the time needed for upgrading the database.
    Truncating SYS.AUD$
    This reduces the time needed for upgrading the database.
    Gathering Oracle Dictionary Statistics
    This reduces the time needed for upgrading the database.
    Running Pre-Upgrade-Information Tool utlu112i.sql
    This is a mandatory task for manual database upgrades.
    This tool is also run in pre_upgrade_status.sql.
    Oracle Database 11.2 Pre-Upgrade Information Tool 08-05-2010 18:24:45                              
    Script Version: 11.2.0.1.0 Build: 003                                                              
    Database:                                                                               
    --> name:          PRD                                                                             
    --> version:       10.2.0.4.0                                                                      
    --> compatible:    10.2.0                                                                          
    --> blocksize:     8192                                                                            
    --> platform:      Microsoft Windows x86 64-bit                                                    
    --> timezone file: V4                                                                               
    Tablespaces: [make adjustments in the current environment]                                         
    --> SYSTEM tablespace is adequate for the upgrade.                                                 
    .... minimum required size: 905 MB                                                                 
    --> PSAPUNDO tablespace is adequate for the upgrade.                                               
    .... minimum required size: 84 MB                                                                  
    --> SYSAUX tablespace is adequate for the upgrade.                                                 
    .... minimum required size: 210 MB                                                                 
    --> PSAPTEMP tablespace is adequate for the upgrade.                                               
    .... minimum required size: 61 MB                                                                  
    Flashback: OFF                                                                               
    Update Parameters: [Update Oracle Database 11.2 init.ora or spfile]                                
    Note: Pre-upgrade tool was run on a lower version 64-bit database.                                 
    --> If Target Oracle is 32-Bit, refer here for Update Parameters:                                  
    -- No update parameter changes are required.                                                       
    --> If Target Oracle is 64-Bit, refer here for Update Parameters:                                  
    WARNING: --> "shared_pool_size" needs to be increased to at least 472 MB                           
    Renamed Parameters: [Update Oracle Database 11.2 init.ora or spfile]                               
    -- No renamed parameters found. No changes are required.                                           
    Obsolete/Deprecated Parameters: [Update Oracle Database 11.2 init.ora or spfile]                   
    --> remote_os_authent            11.1       DEPRECATED                                             
    --> background_dump_dest         11.1       DEPRECATED   replaced by  "diagnostic_dest"            
    --> user_dump_dest               11.1       DEPRECATED   replaced by  "diagnostic_dest"            
    Components: [The following database components will be upgraded or installed]                      
    --> Oracle Catalog Views         [upgrade]  VALID                                                  
    --> Oracle Packages and Types    [upgrade]  VALID                                                  
    Miscellaneous Warnings                                                                             
    WARNING: --> Database is using a timezone file older than version 11.                              
    .... After the release migration, it is recommended that DBMS_DST package                          
    .... be used to upgrade the 10.2.0.4.0 database timezone version                                   
    .... to the latest version which comes with the new release.                                       
    Recommendations                                                                               
    Oracle recommends gathering dictionary statistics prior to                                         
    upgrading the database.                                                                            
    To gather dictionary statistics execute the following command                                      
    while connected as SYSDBA:                                                                               
    EXECUTE dbms_stats.gather_dictionary_stats;                                                                               
    Oracle recommends removing all hidden parameters prior to upgrading.                                                                               
    To view existing hidden parameters execute the following command                                   
    while connected AS SYSDBA:                                                                               
    SELECT name,description from SYS.V$PARAMETER WHERE name                                        
            LIKE '\_%' ESCAPE '\'                                                                               
    Changes will need to be made in the init.ora or spfile.                                                                               
    Oracle recommends reviewing any defined events prior to upgrading.                                                                               
    To view existing non-default events execute the following commands                                 
    while connected AS SYSDBA:                                                                         
      Events:                                                                               
    SELECT (translate(value,chr(13)||chr(10),' ')) FROM sys.v$parameter2                           
          WHERE  UPPER(name) ='EVENT' AND  isdefault='FALSE'                                                                               
    Trace Events:                                                                               
    SELECT (translate(value,chr(13)||chr(10),' ')) from sys.v$parameter2                           
          WHERE UPPER(name) = '_TRACE_EVENTS' AND isdefault='FALSE'                                                                               
    Changes will need to be made in the init.ora or spfile.                                                                               
    PRE-UPGRADE Tasks: === FINISHED ===
    SQL> spool off

  • Do you run Pre-Upgrade Assistant when migrate from 10.1 to 10.2

    Hello,
    I tried to upgrade from 10.1 to 10.2 on Windows. Base on installation guide, you have to install 10.2 in a separate ORACLE_HOME, then run utlu102i.sql through SQL before run DBUA. Since I installed 10.2 without create start database because SID is same as 10.1. How to run pre-upgrade assistant? Or should I setup new SID for 10.2 and change it back after migrate database from 10.1 to 10.2.
    Your assistance will be appreciated,

    I'd suggest to check the "manual upgrade/migration" method described in upgrade doc.
    As a summary:
    utlu102.sql is just a step to verify some prereqs needed before going to 10.2
    You'll need to shutdown your 10.1 DB. Copy your .ora files from 10.1.to 10.2; adjust them appropriately.
    Set your Oracle_home to 10.2; keep same SID. Startup upgrade, then run catpatch.sql (if i remember correctly).
    All these steps are well described in the manual.

  • 11i-R12 upgrade and MOS 954704.1 (pre-upgrade

    I am performing the 11.5.10.2 -> R12.1.1 Upgrade using the Maint Wizard (v2.19) on Linux x86.
    I am at this step:
    Cat - Upg to Rel 12.1.1
    ProdFamily - Perform the Upgrade
    Task - Apply Preinstall Patches
    Step - Check for critical pre-upgrade patches for Financials
    Action - Follows MOS note 954704.1 to apply pre-upgrade patches
    I would like to know whether I need to use any special options/parameters to adpatch when applying these R12 patches.
    Thanks

    I don't understand. I haven't applied ANY R12 patches (except OAS 10.1.2.3) yet since I am still at a "pre-upgrade" step.
    So the R12 patch cannot be in AD_BUGS.
    The R12.AD.A.delta.4 patch is 6510214. Don't I need to know whether it is in the Rapid Install upgrade driver u6678700.drv?Sorry, I thought you are asking how to find if it is applied or not later after the upgrade.
    Just follow the same logic we did with Patch 6856840, search MOS for (R12.AD.A.DELTA.4, Patch 6510214) and you will get the list of patches that includes this patch (according to MOS website, I can see that this patch is only included in R12.AD.A.DELTA.6).
    Thanks,
    Hussein

  • I'm not able to upgrade my Mac to itunes 10.5. Keep getting message "Run pre upgrade script for apple mobile device support" any help please?

    Hi I'm not able to upgrade my Mac OS X 10.5.8 to itunes 10.5 Keep getting message "the following install failed. run pre upgrade script for apple mobile device support" contact software manufacture for assistance. any help please?

    Did you ever figure out the problem? "Contact Software Manufacturer"?? That sounds ominous... I've got the same issue and I'm pretty durn aggravated right about now....
    Thanks!

  • EBS database  pre-upgrade tool

    Hi All,
    I am upgrading EBS database from 10.2.0.3 to 11.2.0.3
    OS - RHEL 5
    EBS - 12.1.3
    While running pre-upgrade too , utl112i.sql am getting some warning. Please help me what step I can follow for this warning.
    WARNING: --> Database contains schemas with objects dependent on DBMS_LDAP package.
    .... Refer to the 11g Upgrade Guide for instructions to configure Network ACLs.
    .... USER APPS has dependent objects.
    Thanks,

    Srini,Hussein.
    Thanks for the update. I have gone through the mentioned link and doc - http://docs.oracle.com/cd/E11882_01/network.112/e16543.pdf.
    I didn't understand properly. And we haven't implement LDAP/AD inegration to EBS. And this DB need a connection other database thorugh DBLINK.
    When I query : select * from dba_dependencies where referenced_name IN ('UTL_TCP','UTL_SMTP','UTL_MAIL','UTL_HTTP','UTL_INADDE','DBMS_LDAP') and owner NOT IN('SYS','PUBLIC','ORDPLUGINS'); Getting a long output. Sorry to put the below.
    APPS OKS_MAIL PACKAGE PUBLIC UTL_SMTP SYNONYM HARD
    APPS MTH_EVENT_PKG PACKAGE BODY PUBLIC UTL_SMTP SYNONYM HARD
    APPS IBY_BANKACCXFR_PUB PACKAGE BODY PUBLIC UTL_TCP SYNONYM HARD
    APPS JTF_DIAGNOSTIC_COREAPI PACKAGE BODY PUBLIC UTL_TCP SYNONYM HARD
    APPS OKS_MAIL PACKAGE BODY PUBLIC UTL_TCP SYNONYM HARD
    APPS WSH_OTM_HTTP_UTL PACKAGE BODY PUBLIC UTL_TCP SYNONYM HARD
    APPS HZ_HTTP_PKG PACKAGE BODY PUBLIC UTL_TCP SYNONYM HARD
    APPS IBY_NETUTILS_PVT PACKAGE BODY PUBLIC UTL_TCP SYNONYM HARD
    APPS IBY_PAYMENT_ADAPTER_PUB PACKAGE BODY PUBLIC UTL_TCP SYNONYM HARD
    APPS IBY_BANKACCXFR_PUB PACKAGE BODY APPS UTL_TCP NON-EXISTENT HARD
    APPS JTF_DIAGNOSTIC_COREAPI PACKAGE BODY APPS UTL_TCP NON-EXISTENT HARD
    APPS OKS_MAIL PACKAGE BODY APPS UTL_TCP NON-EXISTENT HARD
    APPS WSH_OTM_HTTP_UTL PACKAGE BODY APPS UTL_TCP NON-EXISTENT HARD
    APPS HZ_HTTP_PKG PACKAGE BODY APPS UTL_TCP NON-EXISTENT HARD
    APPS IBY_NETUTILS_PVT PACKAGE BODY APPS UTL_TCP NON-EXISTENT HARD
    APPS IBY_PAYMENT_ADAPTER_PUB PACKAGE BODY APPS UTL_TCP NON-EXISTENT HARD
    OWNER NAME TYPE REFERENCED_OWNER REFERENCED_NAME REFERENCED_TYPE REFERENCED_LINK_NAME DEPE
    APPS FND_OID_PLUG PACKAGE BODY APPS DBMS_LDAP NON-EXISTENT HARD
    APPS FND_SSO_REGISTRATION PACKAGE BODY APPS DBMS_LDAP NON-EXISTENT HARD
    APPS FND_LDAP_UTIL PACKAGE APPS DBMS_LDAP NON-EXISTENT HARD
    APPS FND_SSO_REGISTRATION PACKAGE APPS DBMS_LDAP NON-EXISTENT HARD
    APPS FND_LDAP_USER PACKAGE APPS DBMS_LDAP NON-EXISTENT HARD
    APPS FND_OID_PLUG PACKAGE APPS DBMS_LDAP NON-EXISTENT HARD
    APPS FND_OID_UTIL PACKAGE APPS DBMS_LDAP NON-EXISTENT HARD
    APPS WF_OID PACKAGE BODY APPS DBMS_LDAP NON-EXISTENT HARD
    APPS WF_LDAP PACKAGE BODY APPS DBMS_LDAP NON-EXISTENT HARD
    APPS FND_OID_UTIL PACKAGE BODY APPS DBMS_LDAP NON-EXISTENT HARD
    APPS FND_LDAP_UTIL PACKAGE BODY APPS DBMS_LDAP NON-EXISTENT HARD
    APPS WF_OID PACKAGE APPS DBMS_LDAP NON-EXISTENT HARD
    APPS FND_OID_DIAG PACKAGE BODY APPS DBMS_LDAP NON-EXISTENT HARD
    APPS FND_LDAP_USER PACKAGE BODY APPS DBMS_LDAP NON-EXISTENT HARD
    APPS WSH_U_CSPV PACKAGE BODY APPS UTL_HTTP NON-EXISTENT HARD
    APPS MSC_E1APS_UTIL PACKAGE BODY APPS UTL_HTTP NON-EXISTENT HARD
    APPS BIS_CORRECTIVE_ACTION_PVT PACKAGE BODY APPS UTL_HTTP NON-EXISTENT HARD
    APPS HZ_LOCATION_SERVICES_PUB PACKAGE APPS UTL_HTTP NON-EXISTENT HARD
    APPS OKS_MAIL PACKAGE BODY APPS UTL_HTTP NON-EXISTENT HARD
    APPS BIS_PMV_PMF_PVT PACKAGE BO
    Am getting total - 166 rows selected
    Kndly suggest me what I need to do here before upgrade and after upgrade. In the document, need to do some action after upgrade to 11.2.0.3. But I didn't get a clarity what I need to do. I know this showing my lack in security knowledge.
    How important this one and What step I can follow for this output. Do I need to check/consider for this warnings. ?
    Thanks and sorry to ask these problems.

  • Record Count deviation in SLA pre-upgrade

    Hi Everyone
    We have applied SLA pre-upgrade patch for data migration from 11.5.10.2 to 12.1.3.
    Below is the record count we got it after applying SLA pre-upgrade patch in 11.5.10.
    Record count was taken it from “GL_PERIOD_STATUSES” Table.
    154620 with MIGRATION_STATUS_CODE   is   "P"
    123546 with MIGRATION_STATUS_CODE   is “NULL”
    Below is the count, after upgraded it into 11.5.10 to 12.1.3
    125075 with MIGRATION_STATUS_CODE   is   "U"
    153091 with MIGRATION_STATUS_CODE   is “NULL”
    Just let me know, why this much record count deviation happened   and is this right move to go further with this deviation.
    Thanks,
    prasatH.

    please see this
    R12 SLA Upgrade: Check that the SLA Pre-Upgrade Completed Successfully [ID 747216.1]
    NOTE:604893.1 - R12 SLA: FAQ for the R12 SLA Pre-Upgrade Process
    for your count difference please log an SR with oracle
    AppsMAstI
    shairng is Caring

  • SLA Pre-Upgrade program - Post steps

    Dear All,
    We upgrade our oracle applications to R12.1.3 from 11.5.10.2. Before upgrade, we applied the patch patch 5233248 and ran the concurrent program with the below values
    Migrate all sets of books: Yes
    Start Date: “01/01/1976”: Jan-76
    End Date : (Left Blank)
    The above concurrent in 11i insance took only 1 minute. Is this normal ?. There are many steps mentioned in the document R12.0 and R12.1: FAQ for the SLA Upgrade: SLA Pre-Upgrade, Post-Upgrade, and Hot Patch [ID 604893.1] .
    Since I already mentioned to upgrade all GL during the upgrade process itself by mentioning the above parameters in the concurrent program. Do I have to still do anything on this regard after the upgrade
    Please advise

    936074 wrote:
    Thanks Hussein. the pre upgrade program ran only for 1 minute. is this normal ?It should take more time. Please query GL_PERIOD_STATUSES table to verify.
    Thanks,
    Hussein

  • Pre-Upgrade script utlu111i.sql warnings

    Hi Everybody
    Part of the upgrade process from 9i to 11.1.0.7 i ran a utlu111i.sql(11.1 Pre-Upgrade Information Tool) on my 9i(9.2.0.5) db.
    Most of the things checked out okay except for some misc warnings and depreciated pfile settings:
    Miscellaneous Warnings
    WARNING: --> Database contains INVALID objects prior to upgrade.
    .... USER SYS has 18 INVALID objects.
    .... USER SYSADM has 983 INVALID objects.
    .... USER SYSTEM has 1 INVALID objects.
    Can someone tell me how can i check these invalid objects?
    Obsolete/Deprecated Parameters: [Update Oracle Database 11.1 init.ora or spfile]
    --> "hash_join_enabled"
    --> "log_archive_start"
    --> "remote_os_authent"
    --> "background_dump_dest" replaced by "diagnostic_dest"
    --> "user_dump_dest" replaced by "diagnostic_dest"
    --> "core_dump_dest" replaced by "diagnostic_dest"
    what are the replacements for the first 3?
    Thank you

    >
    Can someone tell me how can i check these invalid objects?
    >
    select owner, object_name, object_type from dba_objects where status <> 'VALID' order by 1,2,3;what are the replacements for the first 3?
    >
    hash_join_enabled --> see ML Doc 268581.1 (Obsolete / Deprecated Initialization Parameters in 10.1)
    log_archive_start --> same doc as above
    remote_os_authent --> http://download.oracle.com/docs/cd/B28359_01/server.111/b28320/initparams199.htm#sthref590
    HTH
    Srini

Maybe you are looking for