Pre-upgradarion tool
i am going to migrate and upgrade database from
8.1.7 / 2000 server to 10.2.0.1.0 / OEL
using exp and imp
ie
take exp from source database( 8i )
install OEL / 10.2.0.1.0 IN ANOTHER SERVER create empty datebase with necessary tablespaces.
import the dump file into 10.2.0.1.0.
no problem in downtime ( 9am to 9pm / Monday to saturday) database.
upgradation from 8.1.7 / 2000 server to 10.2.0.1.0/OEL
Can i use utlu102i.sql
copy the sql script a from 10g database and run it in the database to be upgraded database( 8.1.7.0)
or any other method for pre upgradation analysis.
during testing stage it throws error in db link and sequence.
any suggestion please.
Edited by: santhanam_oradba on Aug 3, 2010 7:16 PM
>
... during testing stage it throws error in db link and sequence...
>
We cannot troubleshoot what we cannot see ;-) Pl post the complete error message from relevant logs
HTH
Srini
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 -
Pre verify tool for wireless Java apps - HPUX
Hi wireless gurus,
1. Does Oracle ships a pre verify tool for wireless Java apps for HPUX platform with any of it's products.
2. Please let me know any such tool for HPUX, preferably with a free demo versionHi wireless gurus,
1. Does Oracle ships a pre verify tool for wireless Java apps for HPUX platform with any of it's products.What kind of pre-verify tools are you referring to?
If you are looking something to verify Java code in general, then Jdeveloper has some features built-in for this purpose.
The Oracle9IAS Wireless service designer allows you test, try, and debug wireless apps.
2. Please let me know any such tool for HPUX, preferably with a free demo version -
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. -
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 -
Current State:
• I have a customer running CUCM 6.1 and UCCX 7.01SR5. Currently their CUCM is *NOT* LDAP integrated and using local accounts only. UCCX is AXL integrated to CUCM as usual and is pulling users from CUCM and using CUCM for login validation for CAD.
• The local user accounts in CUCM currently match the naming format in active directory (John Smith in CUCM is jsmith and John Smith is jsmith in AD)
Goal:
• Upgrade software versions and migrate to new hardware for UCCX
• LDAP integrate the CUCM users
Desired Future State and Proposed Upgrade Method
Using the UCCX Pre Upgrade Tool (PUT), backup the current UCCX 7.01 server.
Then during a weekend maintenance window……
• Upgrade the CUCM cluster from 6.1 to 8.0 in 2 step process
• Integrate the CUCM cluster to corporate active directory (LDAP) - sync the same users that were present before, associate with physical phones, select the same ACD/UCCX line under the users settings as before
• Then build UCCX 8.0 server on new hardware and stop at the initial setup stage
• Restore the data from the UCCX PUT tool
• Continue setup per documentation
At this point does UCCX see these agents as the same as they were before?
Is the historical reporting data the same with regards to agent John Smith (local CUCM user) from last week and agent John Smith (LDAP imported CUCM user) from this week ?
I have the feeling that UCCX will see the agents as different almost as if there is a unique identifier that's used in addition to the simple user name.
We can simplify this question along these lines
Starting at the beginning with CUCM 6.1 (local users) and UCCX 7.01. Let's say the customer decided to LDAP integrate the CUCM users and not upgrade any software.
If I follow the same steps with re-associating the users to devices and selecting the ACD/UCCX extension, what happens?
I would guess that UCCX would see all the users it knew about get deleted (making them inactive agents) and the see a whole group of new agents get created.
What would historical reporting show in this case? A set of old agents and a set of new agents treated differently?
Has anyone run into this before?
Is my goal possible while keeping the agent configuration and HR data as it was before?I was doing some more research looking at the DB schema for UCCX 8.
Looking at the Resource table in UCCX, it looks like there is primary key that represents each user.
My question, is this key replicated from CUCM or created locally when the user is imported into UCCX?
How does UCCX determine if user account jsmith in CUCM, when it’s a local account, is different than user account jsmith in CUCM that is LDAP imported?
Would it be possible (with TAC's help most likely) to edit this field back to the previous values so that AQM and historical reporting would think the user accounts are the same?
Database table name: Resource
The Unified CCX system creates a new record in the Resource table when the Unified CCX system retrieves agent information from the Unified CM.
A Resource record contains information about the resource (agent). One such record exists for each active and inactive resource. When a resource is deleted, the old record is flagged as inactive; when a resource is updated, a new record is created and the old one is flagged as inactive. -
Reconciled amounts appears in vendor aging report
Dear all,
When we take report for reconciled transactions,reconciled amounts appears in
aging days(Suppose we have ap invoice in 0-30 days and payments made in 30-60 days it's
already reconciled)
Why it is showing in reconciled aging report ?
JeyakanthanDear，
would like to recommend you to refer to the following note： 1228363-Business Partner Balance does not match journal entries。
In any SAP Business One version lower than 2007, 2 separate
reconciliation engines were employed. One reconciliation engine worked
on the marketing document level, where partial reconciliation was
supported & the other worked on the journal entry level, where only
complete reconciliation was supported.
This duality led in some instances to reconciliation inconsistencies
which were initially highlighted with SAP Business One version 2004
patch level 29, where the red message 'Business Partner balance does not
match journal entries' was displayed when running the ageing report by
sales documents & inconsistencies were detected.
In the year end closing guides (available for download from the
Documentation Resource Centre) SAP have always recommended to run the
ageing reports by journal posting.
In 2006, SAP published note 752261, now retired, documenting the system
behaviour & offering a series of 'Select' queries to aid in
reconciliation inconsistency analysis. These queries were an excellent
tool but now SAP can offer a faster, better & more accurate solution.
In SAP Business One 2007 A & B the reconciliation engines have been
unified & partial reconciliation on journal entry level is now fully
supported. Any database that is upgraded from a lower version undergoes
a complex series of reconciliation upgrade algorithms, where any
reconciliation inconsistency is identified & a reconciliation upgrade
(RU) journal entry is automatically created. This RU journal does not
document any accounting transaction, but simply creates an update in the
'Balance Due' column, thus notionally re-openeing previously
inconsistently reconciled transactions.
These RU journals are then available for internal reconciliation.
Please consult the 2007 Internal Reconciliation Upgrade(IRU)Landing
Page:
Channel Partner Portal -> Solutions -> SAP Business One -> Hot Topics ->
SAP Business One 2007 Information Center -> New Single Reconciliation
Engine- A single engine reconciles the difference and eliminates the
previous reconciliation issue. More
Click on 'More' to be directed to the IRU Landing Page.
Here you will find 'How-to-Guides' in all supported languages, links to
Expert Training Sessions & links to other pertinent information.
You will also find available for download 2007 A & B upgrade simulation
tools. SAP recommends to subject a database that is planned to be
upgraded
This upgrade simulation tool employs all internal reconciliation upgrade
algorithms & the application will display in the 'Internal
Reconciliation Upgrade Audit Trail Report' if a database is affected by
inconcistencies.
Hence, if the message 'Business Partner Balance does not match Journal
Entries' is encountered, proceed as follows:
Option 1:
Upgrade database to SAP Business One 2007 & internally reconcile any RU
journals.
Option 2:
Go to the IRU landing page & download the 'IRU pre-upgrade tool' either
for version 2007A or 2007B, depending on your localisation. Follow the
installation instructions & after successful installation & simulated
upgarde of the database, analyse any inconsistencies appearing with the
help of the How-to-guide. Should a type of inconsistency not have a drop
down arrow & be described as 'Balancing upgrade journal transaction',
the comapny accountant may decide to write it off, should the amount be
insignificant or, if the amount is not insignificant, please log a
support ticket with the component:
SBO-ADM-UT-IAT
Step by step detailed instructions including screenshots of how to
install the sim-tool & what it does can be found on this wiki page:
https://wiki.sdn.sap.com/wiki/display/B1/BPaccountBalancedoesnot+matc
chJournalEntries
Thanks & Regards
Apple -
Road map when migrating uccx 7.0.1 SR5 towards 8.0.2
Folks,
I'm here pretty much to give you a heads up on my road towards migrating uccx 7.0.1 SR5 to 8.0.2:
1) First, I took the backup from my uccx 7.0.1SR5 using the PUT tool (pre-upgrade tool). It is straight forward, no big deal on it. Backup saved on sftp server.
2) Once I did a fresh install on our spare server with 8.0.2, I loaded my PUT backup from sftp...again..no big deal on it. It seemed that everything went fine...
3) When I was doing the tests with the new uccx, 8.0.2, checking scripts...queues...I realized that the calls were not being queued at all..and I was getting an scriptNotFound error.
4) After frustration because I spoke with couple TAC engineers...I had to fix this issue by my own. After research I figured that to fix "scriptNotFound..." there is a trick in which is not documented clearly. When uccx 7 calls a subflow it DOES NOT ADD THE WORD "SCRIPT" in front of it..and on UCCX 8 YOU HAVE TO add the "script' in front of your subflows. After that..no more "scriptNotFound..."error and our application subsystem was no longer in partial service. afff
5) Now, I was told by the people who wrote the cisco upgrade doc that SU2 update for uccx 8 fixes most of the path related issues...again..I did install the patch yesterday..and..everything seemed to be fine..no errors...now im just waiting friday to test it out, and hopefully will be a happy end!
If I miss something here let me know...even if I can help someone..please let me know.
Regards,
Thiago henriquesFolks,
After quite sometime working towards our migration from uccx 7 SR5 to uccx 8.0.2 I finally got it working!!!!wohoooooooooooooooooooooo
Another change was necessary on create file document steo...which is not needed on uccx 8. Me and one TAC engineer (very good one) we removed the "Create File Document". Here it is what the TAC told me:
While accessing an xml document that is uploaded into the document repository, the Create File Document is not needed.
Simply use the Create XML Document (DOC[test.xml]) step to reference the XML document to be read.
If I can help anyone with this, please let me know.
Regards,
Thiago Henriques -
E-Business 12.1.1 Installation Problem
I am having problems installing Oracle E-Business Suite Application version 12.1.1. I am running Windows 2003 Server. I did the following when I tried to install the Application:
1. I downloaded the software from Oracle edelivery website.
2. I unziped the software creating the E:\StageR12
3. I downloaded and installed Cygwin and Visual Studio 2010 Ultimate Edition.
4. I started the rapidwiz without any flags. When it was performing the check, I had a (!) mark next to Systems Tools complaining that it could not find Gnu Make. Did some research on the net and found out that my Cygwin application was not fully installed; therefore, I downloaded ALL the packages and installed them. Renamed gnumake to make.
5. Rechecked and this time it was complaining about the Cl.exe not being available. The Cl.exe is the Visual C++ Command Line complier so I searched for it and it exist in E:\VCPlus\VC\bin. So trying to be smart, I copied Cl.exe to the E:\cygwin\bin. I think this copying was a very wrong move?! I probably should have added the E:\VCPlus\VC\bin into the $PATH environment variable and it would have probably found it.
6. The System Check Passed this time. But in the middle (Step 2 of 5 – about 20%) I had the famous generic error:
RW-50004: Error Code received when running external process. Check log file for details. Running Database Install Driver for VIS instance.
Obviously I have either Abort or Retry. I Retried just to see what happens and the same error popped again?!
7. At this stage I Aborted the installation and the Wizard went through Validating System Configuration. I had an “X” mark next to all of the items except for two items that had an exclamation mark “!”.
Now my question is this:
1. Was the copying of the Visual C++ Complier to Cygwin folder and the absence of E:\VCPlus\VC\bin in the PATH that caused such a crash. I admit the copying was a stupid move to say the least
2. If you need the logs file, please specify where I can find it. I went to E:\Oracle\VIS\inst\apps\VIS_r2d2
and only found a configuration file called conf_VIS.txt. This is obviously a configuration text file and not the installation logs. So my question is this: Where I can find the installation logs? The document 121oaig (Oracle Application Installation Guide) did not mention where to find these logs except how to start/restart your installation and pass the hostname parameters to rapidwiz command.
3. Now what is the best approach to do next? Should I start the installation all over again but first do a clean up? Please direct me to the clean up document and to do an installation clean up? Is removing the E:\Oracle\VIS folder enough to clean the installation or are there registry keys and DB Services and other sort of things that I need to worry about?
4. Another approach is to add the E:\VCPlus\VC\bin in the PATH and run rapidwiz -restart? Would this be a good option?
I appreciate the help to this installation and I am kind of surprised that Oracle wrote their application on Linux even though they are a big supporter of JAVA. This is evident since you need the Cygwin and the Visual C++ compiler as a prerequisite to install the Oracle Applications?!
BTW, I have Oracle Database 11g installed on my machine already this is why I assigned it a different port by setting the port pool to three to avoid any conflict with the existing Oracle DB installation.Hi,
Please check and provide error from log at:-
1. Was the copying of the Visual C++ Complier to Cygwin folder and the absence of E:\VCPlus\VC\bin in the PATH that caused such a crash. I admit the copying was a stupid move to say the leastI also think this is wrong move and copy will not link the libraries. Logs will tell you about it.
For cygwin check below MOS:-
Note 414992.1 Using Cygwin to Maintain E-Business R12 on Windows
2. If you need the logs file, please specify where I can find it. I went to E:\Oracle\VIS\inst\apps\VIS_r2d2 and only found a configuration file called conf_VIS.txt. This is obviously a >configuration text file and not the installation logs. So my question is this: Where I can find the installation logs? The document 121oaig (Oracle Application Installation Guide) did not mention >where to find these logs except how to start/restart your installation and pass the hostname parameters to rapidwiz command.Check for log files from below metalink note:-
How to locate the log files and troubleshoot RapidWiz for R12 [ID 452120.1] -- check first for /tmp ...
paste error here:-
3. Now what is the best approach to do next? Should I start the installation all over again but first do a clean up? Please direct me to the clean up document and to do an installation clean up? Is removing the E:\Oracle\VIS folder enough to clean the installation or are there registry keys and DB Services and other sort of things that I need to worry about?Installation guide:-
http://download.oracle.com/docs/cd/B53825_03/current/acrobat/121oaig.pdf
to cleanup failed env, pls follow below MOS:-
How to Cleanup Windows Environment before Restarting a Failed Installation [ID 156487.1]
I would suggest to:-
1) Clean up exsisting env using MOS i mentioned above.
2) Run MD5 checksup to test your stage area, check bleow MOS:-
MD5 Checksums for R12.1.1 Rapid Install Media [ID 802195.1]
3) Make sure you have all the pre-req tools etc(check guide i mentioned).
4) Start fresh installation.
Thanks,
JD
Edited by: user12001639 on 29 Apr, 2011 5:29 AM -
Database Upgradation from oracle 9.2.0.8 to oracle11gR2
Hi
we are using AIX 5.3 TL 10 SP4 and we are upgrading DB from oracle9.2.0.8 to oracle 11.2.0.2
i am having some doubt from below pre-upgrade scripts out put.
oratst@ebsdevdb on /tmp # sqlplus "/as sysdba"
SQL*Plus: Release 9.2.0.8.0 - Production on Mon Jul 4 10:11:48 2011
Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
Connected to:
Oracle9i Enterprise Edition Release 9.2.0.8.0 - 64bit Production
With the Partitioning, OLAP and Oracle Data Mining options
JServer Release 9.2.0.8.0 - Production
SQL> spool 11202_upgrade.txt
SQL> @utlu112i.sql
Oracle Database 11.2 Pre-Upgrade Information Tool 07-04-2011 10:17:06
Script Version: 11.2.0.2.0 Build: 001
Database:
--> name: EBSTEST
--> version: 9.2.0.8.0
--> compatible: 9.2.0
--> blocksize: 8192
--> timezone file: V1
Logfiles: [make adjustments in the current environment]
--> The existing log files are adequate. No changes are required.
Tablespaces: [make adjustments in the current environment]
--> SYSTEM tablespace is adequate for the upgrade.
.... minimum required size: 8546 MB
--> TOOLS tablespace is adequate for the upgrade.
.... minimum required size: 8 MB
--> TEMP tablespace is adequate for the upgrade.
.... minimum required size: 61 MB
--> AR_TABLE tablespace is adequate for the upgrade.
.... minimum required size: 33497 MB
--> FND_TABLE tablespace is adequate for the upgrade.
.... minimum required size: 45447 MB
--> AMVD tablespace is adequate for the upgrade.
.... minimum required size: 7 MB
--> ASOD tablespace is adequate for the upgrade.
.... minimum required size: 7 MB
--> CCTD tablespace is adequate for the upgrade.
.... minimum required size: 7 MB
--> IBUD tablespace is adequate for the upgrade.
.... minimum required size: 1 MB
--> IEMD tablespace is adequate for the upgrade.
.... minimum required size: 5 MB
--> IEOD tablespace is adequate for the upgrade.
.... minimum required size: 4 MB
--> JTFD tablespace is adequate for the upgrade.
.... minimum required size: 135 MB
--> OKCD tablespace is adequate for the upgrade.
.... minimum required size: 34 MB
--> XDPD tablespace is adequate for the upgrade.
.... minimum required size: 7 MB
--> XNPD tablespace is adequate for the upgrade.
.... minimum required size: 7 MB
--> APPS_UNDOTS1 tablespace is adequate for the upgrade.
.... minimum required size: 849 MB
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:
WARNING: --> "compatible" must be set to at least 10.1.0
--> If Target Oracle is 64-Bit, refer here for Update Parameters:
WARNING: --> "compatible" must be set to at least 10.1.0
WARNING: --> "shared_pool_size" needs to be increased to at least 532 MB
WARNING: --> "java_pool_size" needs to be increased to at least 128 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]
--> optimizer_max_permutations 10.1 OBSOLETE
--> row_locking 10.1 OBSOLETE
--> undo_suppress_errors 10.1 OBSOLETE
--> max_enabled_roles 10.1 DEPRECATED
--> enqueue_resources 10.2 OBSOLETE
--> sql_trace 10.2 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
--> JServer JAVA Virtual Machine [upgrade] VALID
--> Oracle XDK for Java [upgrade] VALID
--> Real Application Clusters [upgrade] INVALID
--> Oracle Text [upgrade] VALID
--> Oracle XML Database [install]
--> Oracle Java Packages [upgrade] VALID
--> Oracle interMedia [upgrade] VALID
--> Spatial [upgrade] VALID
Miscellaneous Warnings
WARNING: --> Passwords exist in some database links.
.... Passwords will be encrypted during the upgrade.
.... Downgrade of database links with passwords is not supported.
WARNING: --> Deprecated CONNECT role granted to some user/roles.
.... CONNECT role after upgrade has only CREATE SESSION privilege.
WARNING: --> Database is using a timezone file older than version 14.
.... After the release migration, it is recommended that DBMS_DST package
.... be used to upgrade the 9.2.0.8.0 database timezone version
.... to the latest version which comes with the new release.
WARNING: --> Database contains INVALID objects prior to upgrade.
.... The list of invalid SYS/SYSTEM objects was written to
.... registry$sys_inv_objs.
.... The list of non-SYS/SYSTEM objects was written to
.... registry$nonsys_inv_objs.
.... Use utluiobj.sql after the upgrade to identify any new invalid
.... objects due to the upgrade.
.... USER ADWANIAH has 1 INVALID objects.
.... USER APPS has 34 INVALID objects.
.... USER CHAKKACHANSA has 1 INVALID objects.
.... USER FA_USER has 9 INVALID objects.
.... USER SYSSEL has 2 INVALID objects.
.... USER SYSTEM has 30 INVALID objects.
.... USER XXITDFINAD has 7 INVALID objects.
WARNING: --> SYSTEM schema default tablespace has been altered.
.... The SYSTEM schema default tablespace is currently set to TOOLS.
.... Prior to upgrading your database please reset the
.... SYSTEM schema default tablespace to SYSTEM using the command:
.... ALTER USER SYSTEM DEFAULT TABLESPACE SYSTEM;
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.
Recommendations
Oracle recommends gathering dictionary statistics prior to
upgrading the database.
To gather dictionary statistics execute the following commands
while connected as SYSDBA:
EXECUTE dbms_stats.gather_schema_stats('CTXSYS',options=>'GATHER'
,estimate_percent=>DBMS_STATS.AUTO_SAMPLE_SIZE
,method_opt=>'FOR ALL COLUMNS SIZE AUTO'
,cascade=>TRUE);
EXECUTE dbms_stats.gather_schema_stats('DBSNMP',options=>'GATHER'
,estimate_percent=>DBMS_STATS.AUTO_SAMPLE_SIZE
,method_opt=>'FOR ALL COLUMNS SIZE AUTO'
,cascade=>TRUE);
EXECUTE dbms_stats.gather_schema_stats('MDSYS',options=>'GATHER'
,estimate_percent=>DBMS_STATS.AUTO_SAMPLE_SIZE
,method_opt=>'FOR ALL COLUMNS SIZE AUTO'
,cascade=>TRUE);
EXECUTE dbms_stats.gather_schema_stats('ORDPLUGINS',options=>'GATHER'
,estimate_percent=>DBMS_STATS.AUTO_SAMPLE_SIZE
,method_opt=>'FOR ALL COLUMNS SIZE AUTO'
,cascade=>TRUE);
EXECUTE dbms_stats.gather_schema_stats('ORDSYS',options=>'GATHER'
estimate_percent=>DBMS_STATS.AUTO_SAMPLE_SIZE
,method_opt=>'FOR ALL COLUMNS SIZE AUTO'
,cascade=>TRUE);
EXECUTE dbms_stats.gather_schema_stats('OUTLN',options=>'GATHER'
,estimate_percent=>DBMS_STATS.AUTO_SAMPLE_SIZE
,method_opt=>'FOR ALL COLUMNS SIZE AUTO'
,cascade=>TRUE);
EXECUTE dbms_stats.gather_schema_stats('SYS',options=>'GATHER'
,estimate_percent=>DBMS_STATS.AUTO_SAMPLE_SIZE
,method_opt=>'FOR ALL COLUMNS SIZE AUTO'
,cascade=>TRUE);
EXECUTE dbms_stats.gather_schema_stats('SYSTEM',options=>'GATHER'
,estimate_percent=>DBMS_STATS.AUTO_SAMPLE_SIZE
,method_opt=>'FOR ALL COLUMNS SIZE AUTO'
,cascade=>TRUE);
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.
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.
SYSAUX Tablespace:
[Create tablespace in the Oracle Database 11.2 environment]
--> New "SYSAUX" tablespace
.... minimum required size for database upgrade: 500 MB
From above output script
1)SYSTEM tablespace is adequate for the upgrade.
.... minimum required size: 8546 MB
From system tablespace minimum required size means free space from system tablespace or total size of system tablespace?
i am going to use dbua utility for upgrade means does it alter tablespace as per output of scripts or we need to manually alter tablespace size as per requirement?
2)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.
what is above warning and how can i configure ACL's for APPS User?
Thanks
With Regards
A-ZHi
oratst@ebsdevdb on /ebdbh/11g/data/cfgtoollogs/dbua/ebstest/upgrade1 # more Upgrade_Directive.log
Connected.
ODMA_DIRECTIVE:VERSION:9.2.0.8
ODMA_DIRECTIVE:MIGRATE_SID:
ODMA_DIRECTIVE:ORA:IGNORE:06512:
ODMA_DIRECTIVE:ORA:FATAL:00600:
ODMA_DIRECTIVE:ORA:FATAL:01012:
ODMA_DIRECTIVE:ORA:FATAL:01031:
ODMA_DIRECTIVE:ORA:FATAL:01034:
ODMA_DIRECTIVE:ORA:FATAL:01078:
ODMA_DIRECTIVE:ORA:FATAL:01092:
ODMA_DIRECTIVE:ORA:FATAL:01109:
ODMA_DIRECTIVE:ORA:FATAL:01119:
ODMA_DIRECTIVE:ORA:FATAL:01507:
ODMA_DIRECTIVE:ORA:FATAL:01722:
ODMA_DIRECTIVE:ORA:FATAL:03113:
ODMA_DIRECTIVE:ORA:FATAL:03114:
ODMA_DIRECTIVE:ORA:FATAL:07445:
ODMA_DIRECTIVE:ORA:FATAL:12560:
ODMA_DIRECTIVE:ORA:RECOVER_TBS:01650:
ODMA_DIRECTIVE:ORA:RECOVER_TBS:01651:
ODMA_DIRECTIVE:ORA:RECOVER_TBS:01652:
ODMA_DIRECTIVE:ORA:RECOVER_TBS:01653:
ODMA_DIRECTIVE:ORA:RECOVER_TBS:01654:
ODMA_DIRECTIVE:ORA:RECOVER_TBS:01655:
ODMA_DIRECTIVE:ORA:RECOVER_ROLL:01562:
ODMA_DIRECTIVE:ORA:RECOVER_INIT:04031:
ODMA_DIRECTIVE:SCRIPT:UPGRADE:rdbms/admin/catupgrd.sql:
ODMA_DIRECTIVE:BOUNCE_DATABASE:UPGRADE:
ODMA_DIRECTIVE:SCRIPT:UPGRADE:rdbms/admin/catuppst.sql:
ODMA_DIRECTIVE:SCRIPT:UPGRADE:sqlplus/admin/help/hlpbld.sql helpus.sql:
Thanks
With Regards
A-Z -
Solve oracle multimedia post upgrade errors
Hello,
I performed and out of place upgrade from oracle 10.2.0.4 to 11.2.0.4.
when I run the postupgrade script i have issues on oracle multimedia that i cannot solve.. it is about shared memory. I followed all the recommendations suggested on the pre-upgrade script.
SQL> @/oracle/product/11.2.0.4/dbhome_1/rdbms/admin/utlu112s.sql
Oracle Database 11.2 Post-Upgrade Status Tool 10-03-2014 15:06:57
Component Current Version Elapsed Time
Name Status Number HH:MM:SS
Oracle Server
. VALID 11.2.0.4.0 00:14:07
JServer JAVA Virtual Machine
. VALID 11.2.0.4.0 00:11:08
Oracle Workspace Manager
. VALID 11.2.0.4.0 00:00:48
Oracle Enterprise Manager
. VALID 11.2.0.4.0 00:09:58
Oracle XDK
. VALID 11.2.0.4.0 00:02:48
Oracle Text
. VALID 11.2.0.4.0 00:00:59
Oracle XML Database
. VALID 11.2.0.4.0 00:05:45
Oracle Database Java Packages
. VALID 11.2.0.4.0 00:00:20
Oracle Multimedia
. ORA-00604: error occurred at recursive SQL level 1 ORA-04031: unable to
allocate 32 bytes of shared memory ("shared pool","select col#, grantee#,
privi...","KGLH0^34b96f2","kglHeapInitialize:temp")
ORA-06512: at
"SYS.DBMS_JAVA", line 655
ORA-06512: at line 1
. ORA-04031: unable to allocate 32 bytes of shared memory ("shared
pool","select col#, grantee#,
privi...","KGLH0^34b96f2","kglHeapInitialize:temp")
ORA-06512: at
"SYS.DBMS_JAVA", line 655
ORA-06512: at line 1
. col#, grantee#, privi...","KGLH0^34b96f2","kglHeapInitialize:temp")
ORA-06512: at "SYS.DBMS_JAVA", line 655
ORA-06512: at line 1
. ORA-06512: at "SYS.DBMS_JAVA", line 655 ORA-06512: at line 1
. ORA-06512: at line 1
. ORA-00604: error occurred at recursive SQL level 1 ORA-04031: unable to
allocate 136 bytes of shared memory ("shared pool","select
i.obj#,i.ts#,i.file#,...","KGLH0^4006e26c","wds: qksmmGetWorkArea")
ORA-06512:
at "SYS.DBMS_JAVA", line 655
ORA-06512: at line 1
. ORA-04031: unable to allocate 136 bytes of shared memory ("shared
pool","select i.obj#,i.ts#,i.file#,...","KGLH0^4006e26c","wds:
qksmmGetWorkArea")
ORA-06512: at "SYS.DBMS_JAVA", line 655
ORA-06512: at line 1
. i.obj#,i.ts#,i.file#,...","KGLH0^4006e26c","wds: qksmmGetWorkArea")
ORA-06512: at "SYS.DBMS_JAVA", line 655
ORA-06512: at line 1
. ORA-06512: at "SYS.DBMS_JAVA", line 655 ORA-06512: at line 1
. ORA-06512: at line 1
. ORA-04045: errors during recompilation/revalidation of
ORDSYS./f87ac59f_DicomEngine
ORA-04031: unable to allocate 32 bytes of shared
memory ("shared pool","ALTER JAVA CLASS
"ORDSYS"."/...","KGLH0^1182baa5","kglHeapInitialize:temp")
ORA-06512: at
"ORDSYS.ORD_DICOM_ADMIN_PRV", line 6945
ORA-06512: at "ORDSYS.ORD_DICOM_ADMIN",
line 276
ORA-06512: at line 1
. ORDSYS./f87ac59f_DicomEngine ORA-04031: unable to allocate 32 bytes of
shared memory ("shared pool","ALTER JAVA CLASS
"ORDSYS"."/...","KGLH0^1182baa5","kglHeapInitialize:temp")
ORA-06512: at
"ORDSYS.ORD_DICOM_ADMIN_PRV", line 6945
ORA-06512: at "ORDSYS.ORD_DICOM_ADMIN",
line 276
ORA-06512: at line 1
. ORA-04031: unable to allocate 32 bytes of shared memory ("shared
pool","ALTER JAVA CLASS
"ORDSYS"."/...","KGLH0^1182baa5","kglHeapInitialize:temp")
ORA-06512: at
"ORDSYS.ORD_DICOM_ADMIN_PRV", line 6945
ORA-06512: at "ORDSYS.ORD_DICOM_ADMIN",
line 276
ORA-06512: at line 1
. JAVA CLASS "ORDSYS"."/...","KGLH0^1182baa5","kglHeapInitialize:temp")
ORA-06512: at "ORDSYS.ORD_DICOM_ADMIN_PRV", line 6945
ORA-06512: at
"ORDSYS.ORD_DICOM_ADMIN", line 276
ORA-06512: at line 1
. ORA-06512: at "ORDSYS.ORD_DICOM_ADMIN_PRV", line 6945 ORA-06512: at
"ORDSYS.ORD_DICOM_ADMIN", line 276
ORA-06512: at line 1
. ORA-06512: at "ORDSYS.ORD_DICOM_ADMIN", line 276 ORA-06512: at line 1
. ORA-06512: at line 1
. ORA-53051: no editDataModel session found ORA-06512: at
"ORDSYS.ORD_DICOM_ADMIN_PRV", line 6306
ORA-06512: at "ORDSYS.ORD_DICOM_ADMIN",
line 125
ORA-06512: at line 14805
. ORA-06512: at "ORDSYS.ORD_DICOM_ADMIN_PRV", line 6306 ORA-06512: at
"ORDSYS.ORD_DICOM_ADMIN", line 125
ORA-06512: at line 14805
. ORA-06512: at "ORDSYS.ORD_DICOM_ADMIN", line 125 ORA-06512: at line 14805
. ORA-06512: at line 14805
. ORA-53051: no editDataModel session found ORA-06512: at
"ORDSYS.ORD_DICOM_ADMIN_PRV", line 6306
ORA-06512: at "ORDSYS.ORD_DICOM_ADMIN",
line 125
ORA-06512: at line 67
. ORA-06512: at "ORDSYS.ORD_DICOM_ADMIN_PRV", line 6306 ORA-06512: at
"ORDSYS.ORD_DICOM_ADMIN", line 125
ORA-06512: at line 67
. ORA-06512: at "ORDSYS.ORD_DICOM_ADMIN", line 125 ORA-06512: at line 67
. INVALID 11.2.0.4.0 00:55:05
Spatial
. OPTION OFF 10.2.0.4.0 00:00:00
Oracle Expression Filter
. VALID 11.2.0.4.0 00:00:16
Oracle Rules Manager
. VALID 11.2.0.4.0 00:00:14
Final Actions
. 00:01:34
Total Upgrade Time: 01:43:11
PL/SQL procedure successfully completed.
thank you
Mario.I explicity set up the sga_target to 668MB as suggested by the pre-upgrade script.
see the output of preugrade tool:
SQL> @/oracle/utlu112i.sql
Oracle Database 11.2 Pre-Upgrade Information Tool 10-02-2014 17:24:25
Script Version: 11.2.0.4.0 Build: 001
Database:
--> name: FUELPLUS
--> version: 10.2.0.4.0
--> compatible: 10.2.0.3.0
--> blocksize: 8192
--> platform: Solaris Operating System (x86-64)
--> timezone file: V4
Tablespaces: [make adjustments in the current environment]
--> SYSTEM tablespace is adequate for the upgrade.
.... minimum required size: 1071 MB
--> UNDOTBS1 tablespace is adequate for the upgrade.
.... minimum required size: 400 MB
--> SYSAUX tablespace is adequate for the upgrade.
.... minimum required size: 804 MB
--> TEMP tablespace is adequate for the upgrade.
.... minimum required size: 60 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:
WARNING: --> "sga_target" needs to be increased to at least 484 MB
--> If Target Oracle is 64-Bit, refer here for Update Parameters:
WARNING: --> "sga_target" needs to be increased to at least 668 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]
--> cursor_space_for_time 11.1 DEPRECATED
--> background_dump_dest 11.1 DEPRECATED replaced by "diagnostic_dest"
--> user_dump_dest 11.1 DEPRECATED replaced by "diagnostic_dest"
--> cursor_space_for_time 11.2 DEPRECATED
Components: [The following database components will be upgraded or installed]
--> Oracle Catalog Views [upgrade] VALID
--> Oracle Packages and Types [upgrade] VALID
--> JServer JAVA Virtual Machine [upgrade] VALID
--> Oracle XDK for Java [upgrade] VALID
--> Oracle Workspace Manager [upgrade] VALID
--> EM Repository [upgrade] VALID
--> Oracle Text [upgrade] VALID
--> Oracle XML Database [upgrade] VALID
--> Oracle Java Packages [upgrade] VALID
--> Oracle interMedia [upgrade] VALID
--> Spatial [upgrade] VALID
--> Data Mining [upgrade] VALID
--> Expression Filter [upgrade] VALID
--> Rule Manager [upgrade] VALID
Miscellaneous Warnings
WARNING: --> Database is using a timezone file older than version 14.
.... 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.
WARNING: --> Database contains INVALID objects prior to upgrade.
.... The list of invalid SYS/SYSTEM objects was written to
.... registry$sys_inv_objs.
.... The list of non-SYS/SYSTEM objects was written to
.... registry$nonsys_inv_objs.
.... Use utluiobj.sql after the upgrade to identify any new invalid
.... objects due to the upgrade.
.... USER PUBLIC has 1 INVALID objects.
WARNING: --> EM Database Control Repository exists in the database.
.... Direct downgrade of EM Database Control is not supported. Refer to the
.... Upgrade Guide for instructions to save the EM data prior to upgrade.
WARNING: --> Your recycle bin is turned on and currently contains no objects.
.... Because it is REQUIRED that the recycle bin be empty prior to upgrading
.... and your recycle bin is turned on, you may need to execute the command:
PURGE DBA_RECYCLEBIN
.... prior to executing your upgrade to confirm the recycle bin is empty.
WARNING: --> JOB_QUEUE_PROCESS value must be updated
.... Your current setting of "10" is too low.
.... Starting with Oracle Database 11g Release 2 (11.2), setting
.... JOB_QUEUE_PROCESSES to 0 causes both DBMS_SCHEDULER and
.... DBMS_JOB jobs to not run. Previously, setting JOB_QUEUE_PROCESSES
.... to 0 caused DBMS_JOB jobs to not run, but DBMS_SCHEDULER jobs were
.... unaffected and would still run. This parameter must be updated to
.... a value greater than 48 (default value is 1000) prior to upgrade.
.... Not doing so will affect the running of utlrp.sql after the upgrade
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 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.
SQL> SPOOL OFF
here are the last 100 lines of upgrade.log
ORA-06512: at "ORDSYS.ORD_DICOM_ADMIN",
line 276
ORA-06512: at line 1
. JAVA CLASS "ORDSYS"."/...","KGLH0^1182baa5","kglHeapInitialize:temp")
ORA-06512: at "ORDSYS.ORD_DICOM_ADMIN_PRV", line 6945
ORA-06512: at
"ORDSYS.ORD_DICOM_ADMIN", line 276
ORA-06512: at line 1
. ORA-06512: at "ORDSYS.ORD_DICOM_ADMIN_PRV", line 6945 ORA-06512: at
"ORDSYS.ORD_DICOM_ADMIN", line 276
ORA-06512: at line 1
. ORA-06512: at "ORDSYS.ORD_DICOM_ADMIN", line 276 ORA-06512: at line 1
. ORA-06512: at line 1
. ORA-53051: no editDataModel session found ORA-06512: at
"ORDSYS.ORD_DICOM_ADMIN_PRV", line 6306
ORA-06512: at "ORDSYS.ORD_DICOM_ADMIN",
line 125
ORA-06512: at line 14805
. ORA-06512: at "ORDSYS.ORD_DICOM_ADMIN_PRV", line 6306 ORA-06512: at
"ORDSYS.ORD_DICOM_ADMIN", line 125
ORA-06512: at line 14805
. ORA-06512: at "ORDSYS.ORD_DICOM_ADMIN", line 125 ORA-06512: at line 14805
. ORA-06512: at line 14805
. ORA-53051: no editDataModel session found ORA-06512: at
"ORDSYS.ORD_DICOM_ADMIN_PRV", line 6306
ORA-06512: at "ORDSYS.ORD_DICOM_ADMIN",
line 125
ORA-06512: at line 67
. ORA-06512: at "ORDSYS.ORD_DICOM_ADMIN_PRV", line 6306 ORA-06512: at
"ORDSYS.ORD_DICOM_ADMIN", line 125
ORA-06512: at line 67
. ORA-06512: at "ORDSYS.ORD_DICOM_ADMIN", line 125 ORA-06512: at line 67
. INVALID 11.2.0.4.0 00:55:05
Spatial
. OPTION OFF 10.2.0.4.0 00:00:00
Oracle Expression Filter
. VALID 11.2.0.4.0 00:00:16
Oracle Rules Manager
. VALID 11.2.0.4.0 00:00:14
Final Actions
. 00:01:34
Total Upgrade Time: 01:43:11
PL/SQL procedure successfully completed.
SQL>
SQL> SET SERVEROUTPUT OFF
SQL> SET VERIFY ON
SQL> commit;
Commit complete.
SQL>
SQL> shutdown immediate;
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL>
SQL>
SQL>
SQL> DOC
DOC>#######################################################################
DOC>#######################################################################
DOC>
DOC> The above sql script is the final step of the upgrade. Please
DOC> review any errors in the spool log file. If there are any errors in
DOC> the spool file, consult the Oracle Database Upgrade Guide for
DOC> troubleshooting recommendations.
DOC>
DOC> Next restart for normal operation, and then run utlrp.sql to
DOC> recompile any invalid application objects.
DOC>
DOC> If the source database had an older time zone version prior to
DOC> upgrade, then please run the DBMS_DST package. DBMS_DST will upgrade
DOC> TIMESTAMP WITH TIME ZONE data to use the latest time zone file shipped
DOC> with Oracle.
DOC>
DOC>#######################################################################
DOC>#######################################################################
DOC>#
SQL>
SQL> Rem Set errorlogging off
SQL> SET ERRORLOGGING OFF;
SQL>
SQL> REM END OF CATUPGRD.SQL
SQL>
SQL> REM bug 12337546 - Exit current sqlplus session at end of catupgrd.sql.
SQL> REM This forces user to start a new sqlplus session in order
SQL> REM to connect to the upgraded db.
SQL> exit -
IDOC Acknowledgement is really available?
Hi there.
I need your help.
In first, my scenario is as follow.
R/3(IDOC) -> XI -> FILE(XML)
I found the acknowledgement from XI to R/3 is automatically generated and send. But it is not proper structure so it is not recognized correctly in R/3.(status 51)
error txt----
IDoc: Invalid table name 'TPSDLS ' in inb. status via IDoc
Message no. EA 863
Diagnosis
When processing the inbound IDoc 0000000008194949 with status records,
the unauthorized name TPSDLS occurred in the field TABNAM.
System Response
IDoc processing terminated with an error.
Procedure
Only the name 'EDI_DS' or the name 'EDI_DS40' can be sent in the field
TABNAM.
cf. TPSDLS is Message Type.
But in XI(SXMB_MONI), outbound message is as follow.
</SAP:Ack>
- <SAP:IDocOutbound xmlns:SAP="http://sap.com/xi/XI/Message/30">
<SAP:TABNAM>EDI_DC40</SAP:TABNAM>
<SAP:MANDT>100</SAP:MANDT>
<SAP:DOCREL>640</SAP:DOCREL>
<SAP:DOCNUM>0000000000000453</SAP:DOCNUM>
<SAP:DIRECT>2</SAP:DIRECT>
<SAP:IDOCTYP>ALEAUD01</SAP:IDOCTYP>
<SAP:CIMTYP />
<SAP:MESTYP>ALEAUD</SAP:MESTYP>
<SAP:MESCOD />
<SAP:MESFCT />
<SAP:SNDPOR>SAPAXP</SAP:SNDPOR>
<SAP:SNDPRN>ADC_UPSTMS</SAP:SNDPRN>
<SAP:SNDPRT>LS</SAP:SNDPRT>
<SAP:SNDPFC />
<SAP:RCVPOR>SAPNAQ</SAP:RCVPOR>
<SAP:RCVPRN>LOG_150</SAP:RCVPRN>
<SAP:RCVPRT>LS</SAP:RCVPRT>
<SAP:RCVPFC />
<SAP:TEST />
<SAP:SERIAL>20060131223008</SAP:SERIAL>
<SAP:EXPRSS />
<SAP:STD />
<SAP:STDVRS />
<SAP:STATUS>03</SAP:STATUS>
<SAP:OUTMOD />
<SAP:SNDSAD />
<SAP:SNDLAD />
<SAP:RCVSAD />
<SAP:RCVLAD />
<SAP:STDMES />
<SAP:REFINT />
<SAP:REFGRP />
<SAP:REFMES />
<SAP:CREDAT>2006-02-01</SAP:CREDAT>
<SAP:CRETIM>03:43:12</SAP:CRETIM>
<SAP:ARCKEY>C758B94092FE11DAA9C9000E7FECFC0E</SAP:ARCKEY>
</SAP:IDocOutbound>
Already I applied OSS NOTE.899200.( It's a bit helpfull)
Someone ask to use BPM, but I want to use this funtion first.
Many thanks for your advice in advance.
BillyHi Naresh,
the version is currently in Ramp-up.
To get a sneak preview you can download the 2007 B pre-upgrade tool. The tool will create an additional sbo-common on your server which faciliates mock-upgrades of databases on the server.
You don't even have to back up a db before subjecting it to the simulated upgrade.
The thus upgraded database is not functional in the sense that you will not be able to add transactions, yet it will allow you to see all existing data & run reports.
We highly recommend to run this pre-upgrade tool on all databases you are planning to upgrade to 2007 B to gauge the IRU impact. You can download the tool & find a multitude of information including a 'How-to-Guide' on the reconciliation landing page:
Go to the 2007 B landing page & then access 'New Reconciliation Engine - Learn more'.
All the best,
Kerstin -
Acrobat Flattening Form Fields and Optimizing for Web
I'm trying to optimize a PDF for the web and flatten all the form fields. I also want to remove the purple dialogue box at the top when optimizing on the web. Has anyone else experienced this problem? I've toiled around with it for some time and can't seem to figure it out. In the older version, I would simply save it as a file optimized for the web, which would then flatten all the form fields and remove the purple box at the top. Any help would be appreciated.
Your question really belongs in one of the Acrobat forums. I flatten form fields (use the pre-flight tool) and then save for the web.
-
Customize "Please update your app from the App Store" message
Please add the possibility to customize/change this message for the branded adobe viewer to include direct link to the app:
"Please update your app
This issue is available for download,
but requires a newer version of the
app. Please update your app from
the App Store."
Thank you,
Gennady!Himanshu,
This just happened to me today with the Adobe Content Viewer and a v22 published app. I updated a folio which was created a while back that was set to "Unspecified" for Viewer Version. It was created originally with pre v20 tools. In both the ACV and a published app this folio showed that "Please update your app..." message when trying to download/view the updated version of the folio. When I got the first update message I was viewing the folio, then I affirmed that I wanted to download the update so it took me to the library view. After trying to initiate the download/update it shows the "please update" error message. I tapped "OK" and then it let me download and view the updated folio. Basically it's showing an error message that doesn't apply. We know it isn't a v23 folio trying to be viewed by a v22 app because my folio version is not even v20, and also because it still lets me download/view the update after it gives the warning. When I've made the mistake of trying to view a newer folio with an older viewer in the past it doesn't let me download/view the new folio, it just gives the error message. Every time I've observed this false error message I've been viewing a folio when I got the initial alert that an updated folio is available. This may or may not be significant/relevant.
Andrew
Maybe you are looking for
-
ERFMG Field in MIGO to be EMpty Initially.
Hello Guys, I currently have a situation where I require the Quantity in UoM (ERFMG) field in MIGO need to be Empty/Zero when the user enters the PO number Initial for movement type 103 only. This should be active only for Goods Receipt->Purchase Ord
-
Multiple Iphones sync with one computer
Can I set up two Iphones to syn with a PC Laptop? How?
-
How can I add my previous icloud storage from my old iTunes ID to my new icloud account
how can I add my previous icloud storage from my old iTunes ID to my new icloud account,
-
My Ipod touch 4g won't turn on!!
Hi, This has happened before, while i was charging it, my iPod slowly turned white, and when i press both the home screen and the on/off button it turned off and went black. The problem is that i can't turn it back on, no matter what i do. It was so
-
It is possible to do real synchron synchronizaton on SAP MI (MAM) ?
Hello I have question about SAP MI / MAM apps and synchron process : SAP MAM or SAP MI own apps synchronization between MI Client and MI server provide with following steps : a) start sync on Client b) every relevant sybcBO object on Server start syn