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

Similar Messages

  • 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

  • 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

  • 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

  • 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

  • Viewer TOTAL record count display CRViewer9

    Post Author: niblick
    CA Forum: General
    A application written in a previous version of Crystal Reports (7 or 8 ?) displays the TOTAL record count in the viewer (not in the report).  I had to upgrade the reports to version 9 (RDC - CRViewer9) and when I preview the report there is no TOTAL record count in the viewer.  How do I enable this in Crystal Reports 9?
    Thanks

    check inbox. forwarded the updated template

  • Maximum record counts and property counts

    Hello,
    I am looking for the document/link that mentions maximum record counts and maximum property counts for each record.
    let say there are 1.5million records and each record has 2000 properties. Not sure if it can be handled nicely.
    Mdex version is 6.2.1 at this point. but can upgrade if higher version can handle more.
    Thanks,

    Jeremy is pretty much correct. There are no limitations except by performance.
    Start with the Performance Tuning Guide - here is a link to the 6.4.1 document:
    http://docs.oracle.com/cd/E41223_01/Mdex.641/pdf/PerfTuningGuide.pdf
    For your questions, start with Chapter 5 and read how properties/dimensions affect performance and this will help drive how you architect your queries and pipeline configuration/index setup to be most efficient.

  • Please help! Invalid node structure and invalid record count

    My MacBook Pro is about 6.5 years old. I upgraded to Snow Leopard 2 years ago and added RAM at the same time. My first problem ever occurred three days ago when my computer got super sluggish, I restarted and got the gray screen with apple and spinning wheel...no boot up. I ran disk utility from the snow leopard install disk and found "invalid node structure" and "invalid record count". After reading on here what to do...try to repair the disk and so on with no success I went out and bought Disk Warrior. Got home expecting to fix everything and Disc Warrior won't boot...I just get a file with a question mark and the disc is ejected. I tried erasing the hard drive but was only able to use the "don't erase data" option. Then I tried to reinstall Snow Leopard with no luck. Now I am stuck. Any ideas? 
    One thing to note is I am to the point of not caring about the files on the hard drive, I was a dummy and never backed them up...lesson learned!  I just want my computer back without having to spend $1000+ for a new one. Then again I am always willing to do that too as a last resort.
    PLEASE HELP!

    When you contact Alsoft, make sure you let them know that you are using Snow Leopard (10.6.8).
    Try the following in the meantime -
    Disconnect all peripherals from your computer.
    Boot from your install disc & run Repair Disk from the utility menu. To use the Install Mac OS X disc, insert the disc, and restart your computer while holding down the C key as it starts up.
    Select your language.
    Once on the desktop, select Utility in the menu bar.
    Select Disk Utility.
    Select the disk or volume in the list of disks and volumes, and then click First Aid.
    Click Repair Disk.
    Restart your computer when done.
    Repair permissions after you reach the desktop-http://support.apple.com/kb/HT2963 and restart your computer.
    Try DiskWarrarior again if it's combatible with the os system.
    YOu cannot reformat until you get your issue corrected.

  • Data Load : Number of records count

    Hi Experts,
              I want to document number of records transferred to BW during an infopackage execution.
              I want to automate the process by running a report in background which will fetch a data from SAP tables about number of records been transfered by all my InfoPackage .
    I would like to know how should I proceed with.
             I want to know some System tables which contains same data as that of RSMO transaction displays to us.
    Kindly help with valuable replies.

    HI,
    inorder to get the record counts report you need to create a report based on below tables
    rsseldone, rsreqdone, rsldpiot, rsmonfact
    Check the below link which explain in detail with the report code as well.
    [Data load Quick Stats|http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/90215bba-9a46-2a10-07a7-c14e97bdb764]
    This doc also explains how to trigger a mail with the details to all.
    Regards
    KP

  • Record count per page , total record count per report in BI Publisher

    hi,
    In Oracle BI Publisher tool , can you please tell me how to display total record count of a report ? as well as how to display record count per page ?
    Thanks for your help
    Regards
    Gayathri

    check inbox. forwarded the updated template

  • 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!

  • Record Count Issue in Search page ?

    Hi Friends
    I am trying to display record count on Search page and I have the following code in
    The table has total of 62 Rows
    AM : for testing purpose, i am printing in log
    public void getISAGRecordCount()
    OAViewObject vo = (OAViewObject)getXXG2_ELIM_ISAGSView1(); //getXXG2ISAGSearchVO1();
    int fetchedRowCount = 0;
    vo.setMaxFetchSize(-1);
    vo.executeQuery();
    fetchedRowCount = vo.getRowCount();
    System.out.println("RowCount: "+ fetchedRowCount);
    IN PFR of CO: I am calling by this way
    am.invokeMethod("getISAGRecordCount");
    the Issue is
    for the first time, when i search  Based on search criteria, I know it should dispaly 10 records  but in the Log file i see the total Record Count of the Table     Ex; 62
    When i do the serach for the second time, based on search criteria, I know it should display 20 records, but the log file has 10 records ( previous search results)
    If I do the search for 3rd time, I see 2nd search results in log
    Any help in this issue, how to fix this?
    Thanks
    Ravi

    Hi,
    Please donot use getRowCount(), use getFetchedRowCount() and remove setMaxFetchSize(-1).
    Hope it will resolve your issue.
    Just for understanding of the concept:
    getFetchedRowCount() returns the number of rows cached in the view object -- including programmatically inserted rows.
    The getRowCount() implicitly execute a query against the database (if a query has not been executed yet)
    Regards,
    Reetesh Sharma

  • Invalid record count - grey screen- Target Mode Cures

    Hi there,
    I have a common problem: I was doing nothing particular that I remember: No fancy file uploads, doanloads, creation, erasing - nothing special:
    Anyway after a customary week, or few days of leaving the macbook permanently on, I think "let's give it a rest".
    Then switch back on:
    - Grey screen, spinning grey progress wheel fine.
    - Takes a while. Strange. After say a minute - it just switches off wordlessly.
    - Reset PRAM: No solution. Take a look with single-user startup in console: Files are all there, OK. Disk not dead.
    - Start up from OS X 10.5 disk:
    Permissions repair fine. Good.
    Verify disk: FAIL! +*Invalid Record Count.Volume check failed.*+
    Next: *Try target disk mode to back up essentials* - that works fine: I now have Time Machine AND a smaller important essentials backup.
    But finally, here's the surprise: Just for kicks, I *shut the macbook down, try a reboot - and it works!*
    But I note that root system files are unchanged since the problem occurred: ".hotfiles.btree" for example (I don't know what that is but suspect it's relevant).
    Then: I tried restarting again - and back to square one, it won't boot.
    Do the "Target disk" firewire mode trick again, and browse a few folders: And it boots (slowly).
    If I just leave the Macbook on permanently - everything seems fine. Not even sluggish.
    So:
    - Why can connecting a disk with an incorrect file system in target disk make the system forget about these problems when booting?
    - Why does the problem return on a successive reboot?
    - Is it related to some system files being ignored if booting straight after a target mode session?
    - What is ".hotfiles.btree", and should it not exist ?
    And the big one:
    - +Can extended Applecare, wot cost me loads of money, help me?+

    Hi Cornelius:
    Having been a faithful Apple-groupie for a while, and despite some problems over the years (hard drive failing, screen going, etc.) this is the first time I'm disappointed with them, because theor Micromat Applecare deal is a ripoff:
    You fork out for Applecare extension: All you get is something that say "Yep, you've got a problem. Now go and buy techtoolpro".
    That is, the TechTool Deluxe is practically useless. Argh.
    Worse: They keep that rather quiet. If you run TechTool deluxe, and it fails: It points you to the Techtool site to
    "download the TechTool Deluxe software with diagnostic and repair capabilities".
    You think "Aha, right, I need an update, or a DMG rather than just the executable".
    Download another 1.25Gb.
    So you try again: Same thing.
    The chiselling little crooks, to quote Ken Livingstone, won't even come out and say "Buy TechTool Pro to fix it". The website as reported above is wrong.
    Result: I'm not happy with them. And I'll never buy anything off Micromat.
    In the meantime, I've got a bootable backup thanks to CC-Cloner (excellent, I'll send him some money), and I'm waiting until I don't have any critical deadlines to allow myself time to restore a daily bootable backup.
    The dodgy files seem to be the Sun Developper Java suite according to CC Cloner.

  • How to find Maximum Record Count in a particular section

    Hi ALL
    My report has  3 detail sections. I am showing different set of data in each section.
    Example:
    Details a
    Details b
    Details c
    In the Details c section  I have 5 columns.
    I want to find out MAXIMUM RECORD COUNT in  only Details c.
    Actually I have done a running total on column1 field which gives me the records number in that section only. But I am not able to find the MAXIMUM record count.
    Rtotal   Colum1   Column 2 Column3
    1          Data1     Data2      Data3
    2          Data1     Data2      Data3
    3          Data1     Data2      Data3
    4          Data1     Data2      Data3
    Now I need the Maximum record count=4
    Thanks.

    If I have understood correctly you want to count the amount of records in each section.
    In this case, go to "Insert > Summary", choose your ID field, and choose "Count" in "Calculate this summary:". You can put the summary in your group footer.
    If you want the maximum (the highest number value in that column), you can choose "Maximum" instead of "Count".

  • Records count in Receiver File Adapter

    Hi All,
    I have a scenario IODC to File. The requirement is to get the total record count in the Trailer record of the Target File .Please help.
    Regards,
    Kevin

    Hello,
    The requirement is to get the total record count in the Trailer record of the Target File
    In your XML, decide which IDOC field you get your records from and then do a similar mapping
    IDOC field -> removeContext -> count -> TrailerRecordfield
    Hope this helps,
    Mark

Maybe you are looking for