Replication Status UNKNOWN?

I have a data suffix serving Solaris configuration information, and the DSCC suffix both configured for multi-master replication over SSL ports. I have tested them in every way that I've been able to think of thus far, and they appear to be working. What is confusing me is the output of the status command (both suffixes show similar output):
$ dsconf show-repl-agmt-status -p 3998 -w /var/opt/SUNWdsee7/dcc/ads/config/dsadmpwd cn=dscc host1.company.com:3999
Unable to bind securely on "host1.company.com:3999" with the specified credentials.
Configuration Status : UNKNOWN
Authentication Status : UNKNOWN
Initialization Status : UNKNOWN
Status : Enabled
Last Update Date : Oct 20, 2010 2:00:26 PM
There are two things bothering me:
First, the "Unable to bind securely" line. If it can't bind securely, then how is the data replicating?
Second, how should I interpret the "UNKNOWN" status? Is this normal with SSL? If not, what should I be looking at?
Thank you,
Chris

If one of the DS instances that you have set replication with is a DS5.x version, status UNKNOWN is an expected behavior.
The reason is dsconf check the remote server for a "magic number" to identify the revision of the server which is a new feature is 6.x and above.

Similar Messages

Logical Standby Creation Problems "Create STatus Unknown"

We are using Grid Control 10.2.0.3 on Oracle 10.2..0.3 databases, Windows 2003 sp2 machines.
We have a primary and fsfo physical standby working properly. We went to create a logical standby on a separate server and had problems. it turned out that the listener on the server was not discovered on the target. we fixed that problem and finished the creation of the logical standby and it seems to be functioning properly now.
However, the status on the data guard page for the logical standby shows Create Status Unknown and we are unable to proceed on to create an additional standby database for other purposes. We have tried removing the logical standby target and re-discovering it but status still shows Create Status Unknown.
Is there any way to clear this status without having to drop the logical standby and completely recreate it.

The status on the agent shows it uploading successfully.
We resolved the issue by removing the logical standby from the configuration and selecting to retain the log apply. We then re-added the standby selecting to manage an existing standby database and the status went to normal.

Java.sql.SQLException:The trans ... no longer active - status: 'Unknown'

Oracle DBA team received a stack trace from our developers about an error generated by a JAVA appilcation using a WebLogic 8.1 application server and a Oracle 9.2.0.8 (RAC) database server with a Linux 2.4 OS. No database errors were logged into the database alert or listener logs, and no trace files were generated by database server on the same day. Developers are still looking for a cause.
Here is the info provided to us by the developers:
Nested StackTrace:
java.sql.SQLException:The transaction is no longer active - status: 'Unknown'. No further JDBC access is allowed within this transaction.
     weblogic.jdbc.wrapper.JTSConnection.checkIfRolledBack(JTSConnection.java:219)
     weblogic.jdbc.wrapper.JTSConnection.checkConnection(JTSConnection.java:228)
     weblogic.jdbc.wrapper.ResultSet.getMetaData(ResultSet.java:184)
     us.tx.state.rrc.common.util.QueryUtils.getSimpleResults(QueryUtils.java:455)
     us.tx.state.rrc.common.util.QueryUtils.executeSimplePS(QueryUtils.java:373)
     us.tx.state.rrc.pr.events.valueobject.BaseLeaseEvent.loadEventData(BaseLeaseEvent.java:182)
     us.tx.state.rrc.pr.events.valueobject.BaseLeaseEvent.loadEvents(BaseLeaseEvent.java:194)
     us.tx.state.rrc.pr.events.valueobject.BaseLeaseEvent.getEvents(BaseLeaseEvent.java:161)
     us.tx.state.rrc.pr.events.PREventManager.getLeaseComingleEvents(PREventManager.java:104)
     us.tx.state.rrc.pr.events.PREventManager.getAllEvents(PREventManager.java:81)
     us.tx.state.rrc.pr.events.process.AutoResolveProcess.createTrxs(AutoResolveProcess.java:80)
     us.tx.state.rrc.process.ejb.session.ProcessManagerSessionBean.initProcess(ProcessManagerSessionBean.java:427)
Application reportedly ran okay when resubmitted later on the same day without any other changes to the environment except a RMAN hot full backup finished before the second run. Developers have been unable to reproduce application error. Any ideas on where the developers should look for a more definitive definition of application errors?

That message is a WLS-resident event. It means that the WLS-managed transaction
for which the thread/JDBC connection was operating, has already finished, whether by
having completed normally or having been rolled back.

OVM 3.1.1 server status "unknown"

Hi
I am in the process of upgrading our clustered environment that consists of 6 servers from ovm 3.0.2 to 3.1.1. Three servers are on 3.1.1 and 3 on 3.0.2 with one in error status - unknown, I can't delete or rediscover the server. Please help
There is one virtual host with status unknown that I did not create on the server.
How can I delete a server with status unknown.
This problem also does not allow me to add or remove other servers.
How can I repair the cluster without restarting all.
I replaced my server name with servername
Thanks
Job Construction Phase
begin()
Appended operation 'Discover Manager Server Discover' to object 'OVM Foundry : Discover Manager'.
commit()
Completed Step: COMMIT
Objects and Operations
Object (IN_USE): [Server] 40:e6:50:88:a2:91:b6:01:01:e8:00:21:5e:c4:8a:a4 (servername)
Object (IN_USE): [DiscoverManager] OVM Foundry : Discover Manager
Operation: Discover Manager Server Discover
Job Running Phase at 12:57 on Mon, Dec 3, 2012
Job Participants: []
Actioner
Starting operation 'Discover Manager Server Discover' on object 'OVM Foundry : Discover Manager'
Setting Context to model only in job with id=1354532262979
Operation 'NTP Service Configure' in non-job running context, not adding it to object '40:e6:50:88:a2:91:b6:01:01:e8:00:21:5e:c4:8a:a4 (servername)'.
Operation 'NTP Service Activate' in non-job running context, not adding it to object '40:e6:50:88:a2:91:b6:01:01:e8:00:21:5e:c4:8a:a4 (servername)'.
Operation 'NTP Service Configure' in non-job running context, not adding it to object '40:e6:50:88:a2:91:b6:01:01:e8:00:21:5e:c4:8a:a4 (servername)'.
Operation 'NTP Service Activate' in non-job running context, not adding it to object '40:e6:50:88:a2:91:b6:01:01:e8:00:21:5e:c4:8a:a4 (servername)'.
Operation 'NTP Service Configure' in non-job running context, not adding it to object '40:e6:50:88:a2:91:b6:01:01:e8:00:21:5e:c4:8a:a4 (servername)'.
Operation 'NTP Service Activate' in non-job running context, not adding it to object '40:e6:50:88:a2:91:b6:01:01:e8:00:21:5e:c4:8a:a4 (servername)'.
Operation 'NTP Service Configure' in non-job running context, not adding it to object '40:e6:50:88:a2:91:b6:01:01:e8:00:21:5e:c4:8a:a4 (servername)'.
Operation 'NTP Service Activate' in non-job running context, not adding it to object '40:e6:50:88:a2:91:b6:01:01:e8:00:21:5e:c4:8a:a4 (servername)'.
Operation 'Bond Port Update' in non-job running context, not adding it to object 'network.BondPort (2) in 40:e6:50:88:a2:91:b6:01:01:e8:00:21:5e:c4:8a:a4 (network.BondPort (2) in servername)'.
Operation 'Bond Mode Update Operation' in non-job running context, not adding it to object 'network.BondPort (2) in 40:e6:50:88:a2:91:b6:01:01:e8:00:21:5e:c4:8a:a4 (network.BondPort (2) in servername)'.
Operation 'VLAN Interface Destruct Operation' in non-job running context, not adding it to object 'network.VlanInterface (3000) in network.BondPort (2) in 40:e6:50:88:a2:91:b6:01:01:e8:00:21:5e:c4:8a:a4'.
Operation 'VLAN Interface Destruct Operation' in non-job running context, not adding it to object 'network.VlanInterface (3001) in network.BondPort (2) in 40:e6:50:88:a2:91:b6:01:01:e8:00:21:5e:c4:8a:a4'.
Operation 'VLAN Interface Destruct Operation' in non-job running context, not adding it to object 'network.VlanInterface (3003) in network.BondPort (2) in 40:e6:50:88:a2:91:b6:01:01:e8:00:21:5e:c4:8a:a4'.
Job Internal Error (Operation)com.oracle.ovm.mgr.api.exception.FailedOperationException: OVMAPI_6055E Discover target: servername, Discover failed with error: com.oracle.odof.exception.ObjectNotFoundException: No such object (level 1): 18696
Mon Dec 03 12:57:53 SAST 2012
at com.oracle.odof.core.storage.ObjectStore.getVessel(ObjectStore.java:1423)
at com.oracle.odof.core.BasicWork.acquireVessel(BasicWork.java:38)
at com.oracle.odof.core.storage.Transaction.acquireVessel(Transaction.java:251)
at com.oracle.odof.core.storage.Transaction.invokeMethod(Transaction.java:794)
at com.oracle.odof.core.Exchange.invokeMethod(Exchange.java:245)
at com.oracle.ovm.mgr.api.virtual.VirtualMachineProxy.getStatusEvent(Unknown Source)
at com.oracle.ovm.mgr.discover.ovm.VirtualMachineDiscoverHandler.process(VirtualMachineDiscoverHandler.java:160)
at com.oracle.ovm.mgr.discover.ovm.VirtualMachineDiscoverHandler.process(VirtualMachineDiscoverHandler.java:32)
at com.oracle.ovm.mgr.discover.ovm.DiscoverHandler.execute(DiscoverHandler.java:66)
at com.oracle.ovm.mgr.discover.DiscoverEngine.handleDiscover(DiscoverEngine.java:461)
at com.oracle.ovm.mgr.discover.DiscoverEngine.handleDiscover(DiscoverEngine.java:446)
at com.oracle.ovm.mgr.discover.DiscoverEngine.handleDiscover(DiscoverEngine.java:430)
at com.oracle.ovm.mgr.discover.DiscoverEngine.handleDefaultDiscover(DiscoverEngine.java:404)
at com.oracle.ovm.mgr.discover.DiscoverEngine.discoverNewServer(DiscoverEngine.java:377)
at com.oracle.ovm.mgr.discover.DiscoverEngine.discoverServer(DiscoverEngine.java:280)
at com.oracle.ovm.mgr.op.manager.DiscoverManagerServerDiscover.action(DiscoverManagerServerDiscover.java:48)
at com.oracle.ovm.mgr.api.collectable.ManagedObjectDbImpl.executeCurrentJobOperationAction(ManagedObjectDbImpl.java:1009)
at com.oracle.odof.core.AbstractVessel.invokeMethod(AbstractVessel.java:330)
at com.oracle.odof.core.AbstractVessel.invokeMethod(AbstractVessel.java:290)
at com.oracle.odof.core.storage.Transaction.invokeMethod(Transaction.java:822)
at com.oracle.odof.core.Exchange.invokeMethod(Exchange.java:245)
at com.oracle.ovm.mgr.api.manager.DiscoverManagerProxy.executeCurrentJobOperationAction(Unknown Source)
at com.oracle.ovm.mgr.api.job.JobEngine.operationActioner(JobEngine.java:218)
at com.oracle.ovm.mgr.api.job.JobEngine.objectActioner(JobEngine.java:309)
at com.oracle.ovm.mgr.api.job.InternalJobDbImpl.objectCommitter(InternalJobDbImpl.java:1140)
at com.oracle.odof.core.AbstractVessel.invokeMethod(AbstractVessel.java:330)
at com.oracle.odof.core.AbstractVessel.invokeMethod(AbstractVessel.java:290)
at com.oracle.odof.core.BasicWork.invokeMethod(BasicWork.java:136)
at com.oracle.odof.command.InvokeMethodCommand.process(InvokeMethodCommand.java:100)
at com.oracle.odof.core.BasicWork.processCommand(BasicWork.java:81)
at com.oracle.odof.core.TransactionManager.processCommand(TransactionManager.java:773)
at com.oracle.odof.core.WorkflowManager.processCommand(WorkflowManager.java:401)
at com.oracle.odof.core.WorkflowManager.processWork(WorkflowManager.java:459)
at com.oracle.odof.io.AbstractClient.run(AbstractClient.java:42)
at java.lang.Thread.run(Thread.java:662)
Mon Dec 03 12:57:53 SAST 2012
at com.oracle.ovm.mgr.discover.DiscoverEngine.handleDiscover(DiscoverEngine.java:478)
at com.oracle.ovm.mgr.discover.DiscoverEngine.handleDiscover(DiscoverEngine.java:446)
at com.oracle.ovm.mgr.discover.DiscoverEngine.handleDiscover(DiscoverEngine.java:430)
at com.oracle.ovm.mgr.discover.DiscoverEngine.handleDefaultDiscover(DiscoverEngine.java:404)
at com.oracle.ovm.mgr.discover.DiscoverEngine.discoverNewServer(DiscoverEngine.java:377)
at com.oracle.ovm.mgr.discover.DiscoverEngine.discoverServer(DiscoverEngine.java:280)
at com.oracle.ovm.mgr.op.manager.DiscoverManagerServerDiscover.action(DiscoverManagerServerDiscover.java:48)
at com.oracle.ovm.mgr.api.collectable.ManagedObjectDbImpl.executeCurrentJobOperationAction(ManagedObjectDbImpl.java:1009)
at com.oracle.odof.core.AbstractVessel.invokeMethod(AbstractVessel.java:330)
at com.oracle.odof.core.AbstractVessel.invokeMethod(AbstractVessel.java:290)
at com.oracle.odof.core.storage.Transaction.invokeMethod(Transaction.java:822)
at com.oracle.odof.core.Exchange.invokeMethod(Exchange.java:245)
at com.oracle.ovm.mgr.api.manager.DiscoverManagerProxy.executeCurrentJobOperationAction(Unknown Source)
at com.oracle.ovm.mgr.api.job.JobEngine.operationActioner(JobEngine.java:218)
at com.oracle.ovm.mgr.api.job.JobEngine.objectActioner(JobEngine.java:309)
at com.oracle.ovm.mgr.api.job.InternalJobDbImpl.objectCommitter(InternalJobDbImpl.java:1140)
at com.oracle.odof.core.AbstractVessel.invokeMethod(AbstractVessel.java:330)
at com.oracle.odof.core.AbstractVessel.invokeMethod(AbstractVessel.java:290)
at com.oracle.odof.core.BasicWork.invokeMethod(BasicWork.java:136)
at com.oracle.odof.command.InvokeMethodCommand.process(InvokeMethodCommand.java:100)
at com.oracle.odof.core.BasicWork.processCommand(BasicWork.java:81)
at com.oracle.odof.core.TransactionManager.processCommand(TransactionManager.java:773)
at com.oracle.odof.core.WorkflowManager.processCommand(WorkflowManager.java:401)
at com.oracle.odof.core.WorkflowManager.processWork(WorkflowManager.java:459)
at com.oracle.odof.io.AbstractClient.run(AbstractClient.java:42)
at java.lang.Thread.run(Thread.java:662)
FailedOperationCleanup
Starting failed operation 'Discover Manager Server Discover' cleanup on object 'OVM Foundry : Discover Manager'
Complete rollback operation 'Discover Manager Server Discover' completed with direction=OVM Foundry : Discover Manager
Rollbacker
Executing rollback operation 'Discover Manager Server Discover' on object 'OVM Foundry : Discover Manager'
Complete rollback operation 'Discover Manager Server Discover' completed with direction=DONE
Objects To Be Rolled Back
Object (IN_USE): [FibreChannelStoragePath] 0x2101001b32b02385 : 0x5005076801404945 (360050768019b824a2800000000000159)
Object (IN_USE): [FibreChannelStoragePath] 0x2101001b32b02385 : 0x5005076801404945 (360050768019b824a2800000000000155)
Object (IN_USE): [Repository] 0004fb00000300007ba011dd2345a105 (OVM3pool1-repos5)
Object (IN_USE): [Server] 00:1a:64:36:12:c2:00:1a:64:36:12:c2:00:1a:64:36 (servername5)
Object (IN_USE): [FibreChannelStoragePath] 0x2101001b32b02385 : 0x5005076801304999 (360050768019b824a2800000000000154)
Object (IN_USE): [LocalFileSystem] 0004fb00000500008ea9dda14f4e661a (fs_OVM3pool1-repos5)
Object (IN_USE): [FibreChannelStoragePath] 0x2101001b32b02385 : 0x5005076801304999 (360050768019b824a2800000000000158)
Object (IN_USE): [Server] 44:45:4c:4c:4b:00:10:4e:80:35:b8:c0:4f:57:34:4a (servername6)
Object (IN_USE): [VlanPortGroup] ERP-VLAN (ERP-VLAN)
Object (IN_USE): [LocalFileSystem] 0004fb0000050000973edd5445656edf (fs_ovm3pool1-repos4)
Object (IN_USE): [FibreChannelStoragePath] 0x2101001b32b02385 : 0x5005076801404945 (360050768019b824a2800000000000157)
Object (DELETING): [VlanInterface] network.VlanInterface (3003) in network.BondPort (2) in 40:e6:50:88:a2:91:b6:01:01:e8:00:21:5e:c4:8a:a4
Object (IN_USE): [FibreChannelStoragePath] 0x2101001b32b0f365 : 0x5005076801104945 (360050768019b824a2800000000000157)
Object (IN_USE): [VlanSegment] network.VlanSegment (3000) in ERP-VLAN
Object (IN_USE): [Server] 80:3d:76:d3:9a:91:b6:01:a4:46:00:21:5e:c4:8a:8c (servername1)
Object (DELETING): [VlanInterface] network.VlanInterface (3001) in network.BondPort (2) in 40:e6:50:88:a2:91:b6:01:01:e8:00:21:5e:c4:8a:a4
Object (IN_USE): [Repository] 0004fb00000300003e182b550289b1bd (OVM3pool1-repos4)
Object (DELETING): [VlanInterface] network.VlanInterface (3000) in network.BondPort (2) in 40:e6:50:88:a2:91:b6:01:01:e8:00:21:5e:c4:8a:a4
Object (DELETING): [FileSystemMount] 40:e6:50:88:a2:91:b6:01:01:e8:00:21:5e:c4:8a:a4_mount_/OVS/Repositories/0004fb00000300007ba011dd2345a105 (ovm3p1host3.up.ac.za_/OVS/Repositories/0004fb00000300007ba011dd2345a105)
Object (IN_USE): [ServerPool] 0004fb000002000006398dfb9ed11968 (OVM3pool1)
Object (IN_USE): [Server] 40:e6:50:88:a2:91:b6:01:01:e8:00:21:5e:c4:8a:a4 (servername)
Object (IN_USE): [FibreChannelStoragePath] 0x2101001b32b0f365 : 0x5005076801204999 (360050768019b824a2800000000000156)
Object (IN_USE): [LocalFileSystem] 0004fb0000050000f117dd7c051b19b2 (fs_OVM3pool1-repos2)
Object (DELETING): [FileSystemMount] 40:e6:50:88:a2:91:b6:01:01:e8:00:21:5e:c4:8a:a4_mount_/OVS/Repositories/0004fb00000300007bb60b6ddfedbe09 (ovm3p1host3.up.ac.za_/OVS/Repositories/0004fb00000300007bb60b6ddfedbe09)
Object (IN_USE): [Cluster] 06398dfb9ed11968
Object (IN_USE): [Server] 44:45:4c:4c:4b:00:10:4e:80:35:b7:c0:4f:57:34:4a (servername4)
Object (IN_USE): [VlanSegment] network.VlanSegment (3001) in ERP-VLAN
Object (CREATED): [IscsiStorageInitiator] iqn.1988-12.com.oracle:33f5536035ff
Object (IN_USE): [BalancerControl] balancer_0004fb000002000006398dfb9ed11968
Object (DELETING): [FileSystemMount] 40:e6:50:88:a2:91:b6:01:01:e8:00:21:5e:c4:8a:a4_mount_/OVS/Repositories/0004fb00000300003e182b550289b1bd (ovm3p1host3.up.ac.za_/OVS/Repositories/0004fb00000300003e182b550289b1bd)
Object (IN_USE): [DiscoverManager] OVM Foundry : Discover Manager
Object (IN_USE): [LocalFileSystem] 0004fb0000050000d7fcaf610852ca6e (fs_OVM3pool1-repos)
Object (DELETING): [FileSystemMount] 40:e6:50:88:a2:91:b6:01:01:e8:00:21:5e:c4:8a:a4_mount_/OVS/Repositories/0004fb00000300004b32fc0f91362450 (ovm3p1host3.up.ac.za_/OVS/Repositories/0004fb00000300004b32fc0f91362450)
Object (DELETING): [IscsiStorageInitiator] iqn.1988-12.com.oracle:d1fcfd4e5e7b
Object (DELETING): [FileSystemMount] 40:e6:50:88:a2:91:b6:01:01:e8:00:21:5e:c4:8a:a4_mount_/OVS/Repositories/0004fb0000030000b28069aee665f468 (ovm3p1host3.up.ac.za_/OVS/Repositories/0004fb0000030000b28069aee665f468)
Object (IN_USE): [BondPort] network.BondPort (2) in 40:e6:50:88:a2:91:b6:01:01:e8:00:21:5e:c4:8a:a4 (network.BondPort (2) in servername)
Object (IN_USE): [Repository] 0004fb00000300007bb60b6ddfedbe09 (OVM3pool1-repos1)
Object (IN_USE): [Repository] 0004fb0000030000b28069aee665f468 (OVM3pool1-repos3)
Object (IN_USE): [FibreChannelStoragePath] 0x2101001b32b02385 : 0x5005076801304999 (360050768019b824a2800000000000156)
Object (IN_USE): [FibreChannelStoragePath] 0x2101001b32b0f365 : 0x5005076801104945 (360050768019b824a2800000000000159)
Object (IN_USE): [LocalFileSystem] 0004fb0000050000a2e5d5d73797f183 (fs_OVM3pool1-repos3)
Object (IN_USE): [FibreChannelStoragePath] 0x2101001b32b0f365 : 0x5005076801204999 (360050768019b824a2800000000000154)
Object (IN_USE): [VlanSegment] network.VlanSegment (3003) in ERP-VLAN
Object (IN_USE): [FibreChannelStoragePath] 0x2101001b32b0f365 : 0x5005076801204999 (360050768019b824a2800000000000158)
Object (IN_USE): [FibreChannelStoragePath] 0x2101001b32b0f365 : 0x5005076801104945 (360050768019b824a2800000000000155)
Object (IN_USE): [EthernetPort] network.EthernetPort (2) in 40:e6:50:88:a2:91:b6:01:01:e8:00:21:5e:c4:8a:a4 with MAC 00:21:5e:c4:8a:a6 (network.EthernetPort (2) in servername)
Write Methods Invoked
Class=InternalJobDbImpl vessel_id=376353 method=addTransactionIdentifier accessLevel=6
Class=DiscoverManagerDbImpl vessel_id=165 method=discoverServer accessLevel=6
Class=ServerDbImpl vessel_id=10073 method=lock accessLevel=6
Class=InternalJobDbImpl vessel_id=376353 method=setCompletedStep accessLevel=6
Class=InternalJobDbImpl vessel_id=376353 method=setAssociatedHandles accessLevel=6
Class=ServerDbImpl vessel_id=10073 method=setEncodedAgentPassword accessLevel=6
Class=ServerDbImpl vessel_id=10073 method=setBootGeneration accessLevel=6
Class=ServerDbImpl vessel_id=10073 method=setManagerUuid accessLevel=6
Class=ServerDbImpl vessel_id=10073 method=setPythonBindingVersion accessLevel=6
Class=ServerDbImpl vessel_id=10073 method=removeAllNtpServers accessLevel=6
Class=ServerDbImpl vessel_id=10073 method=addNtpServer accessLevel=6
Class=ServerDbImpl vessel_id=10073 method=addNtpServer accessLevel=6
Class=ServerDbImpl vessel_id=10073 method=addNtpServer accessLevel=6
Class=ServerDbImpl vessel_id=10073 method=setNtpServiceState accessLevel=6
Class=ServerDbImpl vessel_id=10073 method=setServerPool accessLevel=6
Class=ServerPoolDbImpl vessel_id=4157 method=removeServer accessLevel=6
Class=ServerDbImpl vessel_id=10073 method=lock accessLevel=6
Class=BalancerControlDbImpl vessel_id=4169 method=removeServer accessLevel=6
Class=ClusterDbImpl vessel_id=4163 method=deallocateSlotForServer accessLevel=6
Class=ServerDbImpl vessel_id=10073 method=clearServerRoles accessLevel=6
Class=ServerDbImpl vessel_id=10073 method=setCluster accessLevel=6
Class=ClusterDbImpl vessel_id=4163 method=removeServer accessLevel=6
Class=ServerDbImpl vessel_id=2798 method=lock accessLevel=6
Class=ServerDbImpl vessel_id=10073 method=lock accessLevel=6
Class=ServerDbImpl vessel_id=13920 method=lock accessLevel=6
Class=ServerDbImpl vessel_id=134016 method=lock accessLevel=6
Class=ServerDbImpl vessel_id=325394 method=lock accessLevel=6
Class=ServerDbImpl vessel_id=10073 method=setSupportedApiVersions accessLevel=6
Class=ServerDbImpl vessel_id=10073 method=lock accessLevel=6
Class=ServerDbImpl vessel_id=10073 method=deleteStorageInitiator accessLevel=6
Class=IscsiStorageInitiatorDbImpl vessel_id=10274 method=setLifecycleState accessLevel=6
Class=IscsiStorageInitiatorDbImpl vessel_id=10274 method=setRollbackLifecycleState accessLevel=6
Class=IscsiStorageInitiatorDbImpl vessel_id=10274 method=onPersistableClean accessLevel=6
Class=ServerDbImpl vessel_id=10073 method=deleteStorageInitiator accessLevel=6
Class=ServerDbImpl vessel_id=10073 method=createStorageInitiator accessLevel=6
Class=IscsiStorageInitiatorDbImpl vessel_id=376363 method=setName accessLevel=6
Class=IscsiStorageInitiatorDbImpl vessel_id=376363 method=setFoundryContext accessLevel=6
Class=IscsiStorageInitiatorDbImpl vessel_id=376363 method=onPersistableCreate accessLevel=6
Class=IscsiStorageInitiatorDbImpl vessel_id=376363 method=setLifecycleState accessLevel=6
Class=IscsiStorageInitiatorDbImpl vessel_id=376363 method=setRollbackLifecycleState accessLevel=6
Class=ServerDbImpl vessel_id=10073 method=lock accessLevel=6
Class=EthernetPortDbImpl vessel_id=10286 method=setDetails accessLevel=6
Class=BondPortDbImpl vessel_id=10415 method=removeEthernetPort accessLevel=6
Class=EthernetPortDbImpl vessel_id=10286 method=setBondPort accessLevel=6
Class=BondPortDbImpl vessel_id=10415 method=setMode accessLevel=6
Class=BondPortDbImpl vessel_id=10415 method=setMediaAccessControlAddress accessLevel=6
Class=VlanPortGroupDbImpl vessel_id=3960 method=removeNetworkPort accessLevel=6
Class=BondPortDbImpl vessel_id=10415 method=setNetworkPortGroup accessLevel=6
Class=BondPortDbImpl vessel_id=10415 method=setJobAsset accessLevel=6
Class=BondPortDbImpl vessel_id=10415 method=deleteVlanInterface accessLevel=6
Class=VlanInterfaceDbImpl vessel_id=10435 method=setLifecycleState accessLevel=6
Class=VlanInterfaceDbImpl vessel_id=10435 method=setRollbackLifecycleState accessLevel=6
Class=VlanInterfaceDbImpl vessel_id=10435 method=onPersistableClean accessLevel=6
Class=VlanSegmentDbImpl vessel_id=3965 method=removeVlanInterface accessLevel=6
Class=BondPortDbImpl vessel_id=10415 method=deleteVlanInterface accessLevel=6
Class=BondPortDbImpl vessel_id=10415 method=deleteVlanInterface accessLevel=6
Class=BondPortDbImpl vessel_id=10415 method=deleteVlanInterface accessLevel=6
Class=VlanInterfaceDbImpl vessel_id=10440 method=setLifecycleState accessLevel=6
Class=VlanInterfaceDbImpl vessel_id=10440 method=setRollbackLifecycleState accessLevel=6
Class=VlanInterfaceDbImpl vessel_id=10440 method=onPersistableClean accessLevel=6
Class=VlanSegmentDbImpl vessel_id=3982 method=removeVlanInterface accessLevel=6
Class=BondPortDbImpl vessel_id=10415 method=deleteVlanInterface accessLevel=6
Class=BondPortDbImpl vessel_id=10415 method=deleteVlanInterface accessLevel=6
Class=BondPortDbImpl vessel_id=10415 method=deleteVlanInterface accessLevel=6
Class=VlanInterfaceDbImpl vessel_id=10445 method=setLifecycleState accessLevel=6
Class=VlanInterfaceDbImpl vessel_id=10445 method=setRollbackLifecycleState accessLevel=6
Class=VlanInterfaceDbImpl vessel_id=10445 method=onPersistableClean accessLevel=6
Class=VlanSegmentDbImpl vessel_id=3997 method=removeVlanInterface accessLevel=6
Class=BondPortDbImpl vessel_id=10415 method=deleteVlanInterface accessLevel=6
Class=BondPortDbImpl vessel_id=10415 method=deleteVlanInterface accessLevel=6
Class=ServerDbImpl vessel_id=10073 method=lock accessLevel=6
Class=ServerDbImpl vessel_id=10073 method=lock accessLevel=6
Class=ServerDbImpl vessel_id=10073 method=setDistributedAsset accessLevel=6
Class=HashMapDbImpl vessel_id=10078 method=remove accessLevel=6
Class=FibreChannelStoragePathDbImpl vessel_id=16925 method=setMultipathDevice accessLevel=6
Class=FibreChannelStoragePathDbImpl vessel_id=10357 method=setMultipathDevice accessLevel=6
Class=FibreChannelStoragePathDbImpl vessel_id=10326 method=setMultipathDevice accessLevel=6
Class=FibreChannelStoragePathDbImpl vessel_id=16918 method=setMultipathDevice accessLevel=6
Class=FibreChannelStoragePathDbImpl vessel_id=13609 method=setMultipathDevice accessLevel=6
Class=FibreChannelStoragePathDbImpl vessel_id=10351 method=setMultipathDevice accessLevel=6
Class=FibreChannelStoragePathDbImpl vessel_id=13615 method=setMultipathDevice accessLevel=6
Class=FibreChannelStoragePathDbImpl vessel_id=10333 method=setMultipathDevice accessLevel=6
Class=FibreChannelStoragePathDbImpl vessel_id=16931 method=setMultipathDevice accessLevel=6
Class=FibreChannelStoragePathDbImpl vessel_id=10339 method=setMultipathDevice accessLevel=6
Class=FibreChannelStoragePathDbImpl vessel_id=16937 method=setMultipathDevice accessLevel=6
Class=FibreChannelStoragePathDbImpl vessel_id=10345 method=setMultipathDevice accessLevel=6
Class=RepositoryDbImpl vessel_id=17130 method=removePresentedServer accessLevel=6
Class=RepositoryDbImpl vessel_id=17019 method=removePresentedServer accessLevel=6
Class=RepositoryDbImpl vessel_id=13642 method=removePresentedServer accessLevel=6
Class=RepositoryDbImpl vessel_id=4254 method=removePresentedServer accessLevel=6
Class=ServerDbImpl vessel_id=10073 method=lock accessLevel=6
Class=ServerDbImpl vessel_id=10073 method=deleteFileSystemMount accessLevel=6
Class=FileSystemMountDbImpl vessel_id=10597 method=setLifecycleState accessLevel=6
Class=FileSystemMountDbImpl vessel_id=10597 method=setRollbackLifecycleState accessLevel=6
Class=FileSystemMountDbImpl vessel_id=10597 method=onPersistableClean accessLevel=6
Class=LocalFileSystemDbImpl vessel_id=4248 method=removeFileSystemMount accessLevel=6
Class=ServerDbImpl vessel_id=10073 method=deleteFileSystemMount accessLevel=6
Class=FileSystemMountDbImpl vessel_id=10613 method=setLifecycleState accessLevel=6
Class=FileSystemMountDbImpl vessel_id=10613 method=setRollbackLifecycleState accessLevel=6
Class=FileSystemMountDbImpl vessel_id=10613 method=onPersistableClean accessLevel=6
Class=LocalFileSystemDbImpl vessel_id=7145 method=removeFileSystemMount accessLevel=6
Class=ServerDbImpl vessel_id=10073 method=deleteFileSystemMount accessLevel=6
Class=FileSystemMountDbImpl vessel_id=13699 method=setLifecycleState accessLevel=6
Class=FileSystemMountDbImpl vessel_id=13699 method=setRollbackLifecycleState accessLevel=6
Class=FileSystemMountDbImpl vessel_id=13699 method=onPersistableClean accessLevel=6
Class=LocalFileSystemDbImpl vessel_id=13636 method=removeFileSystemMount accessLevel=6
Class=ServerDbImpl vessel_id=10073 method=deleteFileSystemMount accessLevel=6
Class=FileSystemMountDbImpl vessel_id=17088 method=setLifecycleState accessLevel=6
Class=FileSystemMountDbImpl vessel_id=17088 method=setRollbackLifecycleState accessLevel=6
Class=FileSystemMountDbImpl vessel_id=17088 method=onPersistableClean accessLevel=6
Class=LocalFileSystemDbImpl vessel_id=17013 method=removeFileSystemMount accessLevel=6
Class=ServerDbImpl vessel_id=10073 method=deleteFileSystemMount accessLevel=6
Class=FileSystemMountDbImpl vessel_id=17197 method=setLifecycleState accessLevel=6
Class=FileSystemMountDbImpl vessel_id=17197 method=setRollbackLifecycleState accessLevel=6
Class=FileSystemMountDbImpl vessel_id=17197 method=onPersistableClean accessLevel=6
Class=LocalFileSystemDbImpl vessel_id=17124 method=removeFileSystemMount accessLevel=6
Class=DiscoverManagerDbImpl vessel_id=165 method=nextJobOperation accessLevel=6
Class=InternalJobDbImpl vessel_id=376353 method=setFailedOperation accessLevel=6
Class=ServerDbImpl vessel_id=10073 method=nextJobOperation accessLevel=6
Class=DiscoverManagerDbImpl vessel_id=165 method=nextJobOperation accessLevel=6
Class=DiscoverManagerDbImpl vessel_id=165 method=nextJobOperation accessLevel=6
Completed Step: ROLLBACK
Job failed commit (internal) due to OVMAPI_6055E Discover target: ovm3p1host3.up.ac.za, Discover failed with error: com.oracle.odof.exception.ObjectNotFoundException: No such object (level 1): 18696
Mon Dec 03 12:57:53 SAST 2012
at com.oracle.odof.core.storage.ObjectStore.getVessel(ObjectStore.java:1423)
at com.oracle.odof.core.BasicWork.acquireVessel(BasicWork.java:38)
at com.oracle.odof.core.storage.Transaction.acquireVessel(Transaction.java:251)
at com.oracle.odof.core.storage.Transaction.invokeMethod(Transaction.java:794)
at com.oracle.odof.core.Exchange.invokeMethod(Exchange.java:245)
at com.oracle.ovm.mgr.api.virtual.VirtualMachineProxy.getStatusEvent(Unknown Source)
at com.oracle.ovm.mgr.discover.ovm.VirtualMachineDiscoverHandler.process(VirtualMachineDiscoverHandler.java:160)
at com.oracle.ovm.mgr.discover.ovm.VirtualMachineDiscoverHandler.process(VirtualMachineDiscoverHandler.java:32)
at com.oracle.ovm.mgr.discover.ovm.DiscoverHandler.execute(DiscoverHandler.java:66)
at com.oracle.ovm.mgr.discover.DiscoverEngine.handleDiscover(DiscoverEngine.java:461)
at com.oracle.ovm.mgr.discover.DiscoverEngine.handleDiscover(DiscoverEngine.java:446)
at com.oracle.ovm.mgr.discover.DiscoverEngine.handleDiscover(DiscoverEngine.java:430)
at com.oracle.ovm.mgr.discover.DiscoverEngine.handleDefaultDiscover(DiscoverEngine.java:404)
at com.oracle.ovm.mgr.discover.DiscoverEngine.discoverNewServer(DiscoverEngine.java:377)
at com.oracle.ovm.mgr.discover.DiscoverEngine.discoverServer(DiscoverEngine.java:280)
at com.oracle.ovm.mgr.op.manager.DiscoverManagerServerDiscover.action(DiscoverManagerServerDiscover.java:48)
at com.oracle.ovm.mgr.api.collectable.ManagedObjectDbImpl.executeCurrentJobOperationAction(ManagedObjectDbImpl.java:1009)
at com.oracle.odof.core.AbstractVessel.invokeMethod(AbstractVessel.java:330)
at com.oracle.odof.core.AbstractVessel.invokeMethod(AbstractVessel.java:290)
at com.oracle.odof.core.storage.Transaction.invokeMethod(Transaction.java:822)
at com.oracle.odof.core.Exchange.invokeMethod(Exchange.java:245)
at com.oracle.ovm.mgr.api.manager.DiscoverManagerProxy.executeCurrentJobOperationAction(Unknown Source)
at com.oracle.ovm.mgr.api.job.JobEngine.operationActioner(JobEngine.java:218)
at com.oracle.ovm.mgr.api.job.JobEngine.objectActioner(JobEngine.java:309)
at com.oracle.ovm.mgr.api.job.InternalJobDbImpl.objectCommitter(InternalJobDbImpl.java:1140)
at com.oracle.odof.core.AbstractVessel.invokeMethod(AbstractVessel.java:330)
at com.oracle.odof.core.AbstractVessel.invokeMethod(AbstractVessel.java:290)
at com.oracle.odof.core.BasicWork.invokeMethod(BasicWork.java:136)
at com.oracle.odof.command.InvokeMethodCommand.process(InvokeMethodCommand.java:100)
at com.oracle.odof.core.BasicWork.processCommand(BasicWork.java:81)
at com.oracle.odof.core.TransactionManager.processCommand(TransactionManager.java:773)
at com.oracle.odof.core.WorkflowManager.processCommand(WorkflowManager.java:401)
at com.oracle.odof.core.WorkflowManager.processWork(WorkflowManager.java:459)
at com.oracle.odof.io.AbstractClient.run(AbstractClient.java:42)
at java.lang.Thread.run(Thread.java:662)
...

Thank you user9352542
I followed the following commands and was able to remove the server from the cluster.
Tahks again
Ran as follows:
/etc/init.d/ovmm stop
NOTE: cat /u01/app/oracle/ovm-manager-3/.config (This provides some of the info you need to connect to your db if you have forgotten.)
cd /u01/app/oracle/ovm-manager-3/bin/
./ovm_upgrade.sh fixup dbhost=localhost dbport=1521 dbsid=OVM dbuser=ovs dbpass=password
This ran fixed errors.
Restarted OVM Manager:
/etc/init.d/ovmm start

SQL 2012 Transactional Replication Publisher is also AG Primary, AG fine, but Replication status continuously 'waiting for next Log backup'

Hi,
I have a SQL 2012 instance that hosts 3 databases that are publishers in (push) transactional replication to subscribers in other domains and are also primary in an Availability Group to other instances in the same domain. The AG is healty (synchronized),
and replication is ok for 2 databases, but the third continuously shows the Publisher to Distributor history status as 'Replicated transactions are waiting for next Log backup or for mirroring to catch up.'
I have weekly full, nightly differential, and hourly log. Those are running and I've tested restoring the publisher db from them into a test instance. The option for sync_with_backup is 0. I generated a new snapshot, no change (haven't
reinitialized, that will be last possible option as this is production). When the log backups run, status will briefly change to 'Approximately (x) log records have been scanned in pass # ..., 0 of which were marked for replication' and some data
does replicate, but then status immediately changes back to the message about waiting for log backup. We are only replicating tables (no views, sp's, etc). All subscribers and AG secondaries are SQL 2012. My db is less than 200
GB data.
The jobs are continuously running and data updates are occurring on the primary. The distribution database is on the same instance as the publishers. Anyone have any ideas what could be happening?
Thanks greatly!

Update - I resolved this.
We had added a new asynchronous instance to the AG, but hadn't added the databases on the new node to the AG yet. Conceptually it seems that adding the instance must have marked the logs and interferred with transactional replication on the
primary. Once I added the databases to the AG on the secondary, then the replication status cleared on the primary and has remained cleared. It is odd though that it only impacted one of the databases in the AG.
cheers.

DB12 - Archiving directory status unknown

Hi,
In DB12 we are getting 'Archiving directory status - unknown'.
OS06 refresh data available as normal. We stopped and restarted SAPOSCOL from OS06 and from OSlevel with saposcol -l and saposcol -k command, but still same issue.
Ours is solaris cluster, pls suggest
Regards

Hello,
Following SAP Notes might help you
Note 199586 - Missing free space value in DB12
Note 536954 - OS data in a cluster environment for OS07
Thanks

InfoPackage error message "Subsequent update (requests) : Status unknown "

After running an InfoPackage the status is set to green, but when you look at the Details tab you see an error message "Subsequent update (requests) : Status unknown " and "With DTP in InfoProvider ZHRPYO00 : Further processed " under it. We did not used to get this error message and don't quite understand why are we getting it now. Could someone explain, please?
Thanks!
Luda

Hi,
Usually this error could be while loading the DSO or loading DSO first and then to other infoprovider.
Error message tab at the monitor should give you clear error message where it went wrong. check this tab.
some time while activating the data this may fail for the DSO object. or some time due to authorization problem to load the data automatically from the DSO to infocubes.
If possible let me know what is error message.
Regards,
Vishwa.

ORA-12514 & Listener Status Instance status Unknown issue

Dear All,
Database Version - 10.2.0.5.0
Operating System - Windows XP
I am using Oracle 10g version, which has two services (bit10g and ora10g) installed on it.
Service ora10g was working before upgradation of Database to 10.2.0.5.0 and it was fine.
On upgradation I was unable to start and connect using ora10g so I created another that is bit10g.
Service bit10g was working fine for quite a long time. The last I worked and connected was on thu and it was connecting with no issues.
Now when I am trying to connect to database today I am unable to connect as I am getting
ORA12514 - TNS:listener does not currently know of service.
Secondly I tried to search forums which guided me to check the Listener Status.
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Admin>lsnrctl status
LSNRCTL for 32-bit Windows: Version 10.2.0.5.0 - Production on 12-JAN-2013 11:42
:54
Copyright (c) 1991, 2010, Oracle. All rights reserved.
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=toshiba-arif)(PORT=1521)
STATUS of the LISTENER
Alias                     LISTENER
Version                   TNSLSNR for 32-bit Windows: Version 10.2.0.5.0 - Produ
ction
Start Date                12-JAN-2013 11:18:12
Uptime                    0 days 0 hr. 24 min. 43 sec
Trace Level               off
Security                  ON: Local OS Authentication
SNMP                      OFF
Listener Parameter File   C:\ora10g\product\10.2.0\db_1\network\admin\listener.o
ra
Listener Log File         C:\ora10g\product\10.2.0\db_1\network\log\listener.log
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=toshiba-arif)(PORT=1521)))
Services Summary...
Service "Oracle8" has 1 instance(s).
Instance "bit10g", status UNKNOWN, has 1 handler(s) for this service...
The command completed successfullyFollowing is my listener.ora file
# listener.ora Network Configuration File: C:\ora10g\product\10.2.0\db_1\NETWORK\ADMIN\listener.ora
# Generated by Oracle configuration tools.
SID_LIST_LISTENER =
(SID_LIST =
    (SID_DESC =
      (GLOBAL_DBNAME = Oracle8)
      (SID_NAME = bit10g)
LISTENER =
(DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST = toshiba-arif)(PORT = 1521))
)Please note that I am a developer with no DBA exposure.
So please guide me so that I will be able to resolve my issue.
Thanks & Regards
Arif Khadas

Once again Thanks Paul for your quick response.
I also have Oracle 9i installed on my machine but the service and Listener for 9i is stopped.
Following is the tnsnames.ora for 9i
# TNSNAMES.ORA Network Configuration File: C:\oracle\ora92\NETWORK\ADMIN\tnsnames.ora
# Generated by Oracle configuration tools.
BIT10G =
(DESCRIPTION =
(ADDRESS =
(PROTOCOL = TCP)
(HOST = toshiba-arif)
(PORT = 1521)
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = bit10g)
BIT_ORA9I =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = IAS)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = ORA9I)
ORA10G =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = toshiba-arif)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = ora10g)
ORA9I =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = toshiba-arif)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = ora9i)
INST1_HTTP =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = AH-IBM)(PORT = 1521))
(CONNECT_DATA =
(SERVER = SHARED)
(SERVICE_NAME = MODOSE)
(PRESENTATION = http://HRService)
CRCPROD =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = 192.1.1.185)(PORT = 1521))
(CONNECT_DATA =
(SERVICE_NAME = bridges)
IAS_ORA10G =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = IAS)(PORT = 1522))
(CONNECT_DATA =
(SID = ORA10G)
EXTPROC_CONNECTION_DATA =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC0))
(CONNECT_DATA =
(SID = PLSExtProc)
(PRESENTATION = RO)
BIT_ORA10G =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = IAS)(PORT = 1522))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = ORA10G)
)

PLSExtProc", status UNKNOWN

Hi Friends,
I check lsnrctl status and ont item that i can not understand it.
Service "PLSExtProc" has 1 instance(s).
Instance "PLSExtProc", status UNKNOWN, has 1 handler(s) for this service...
What means is for this item?
Thanks,
Jim

check this link out...looks like he had similar problem...
Re: Instance "PLSExtProc", status UNKNOWN, has 1 handler(s) for this servic

Instance "orcl", status UNKNOWN, has 1 handler(s) for this service...

Service "orcl" has 2 instance(s).
Instance "orcl", status UNKNOWN, has 1 handler(s) for this service...
Instance "orcl", status READY, has 3 handler(s) for this service...
Service "rcat" has 2 instance(s).
Instance "rcat", status UNKNOWN, has 1 handler(s) for this service...
Instance "rcat", status READY, has 1 handler(s) for this service...
What does Instance "orcl", status UNKNOWN, has 1 handler(s) for this service... means?

Table 10-3 Listener Control Utility SERVICES Command
Output Section Description
Service
Identifies the registered service
Instance
Specifies the name of the instance associated with the service
The status field indicates if the instance is able to accept connections.
A READY status means that the instance can accept connections.
A BLOCKED status means that the instance cannot accept connections.
A READY/SECONDARY status means that the is a secondary instance in an Oracle Real Application Clusters primary/secondary configuration and is ready to accept connections.
A RESTRICTED status means that the instance is in restricted mode. The listener blocks all connections to this instance.
An UNKNOWN status means that the instance is registered statically in the listener.ora file rather than dynamically with service registration. Therefore, the status is non known.
Handlers
Identifies the name of the service handler. Dispatchers are named D000 through D999. Dedicated servers have a name of DEDICATED.
This section also identifies the following about the service handler:
established: The number of client connections this service handler has established
refused: The number of client connections it has refused
current: The number of client connections it is handling, that is, its current load
max: The maximum number of connections for the service handler, that is, its maximum load
state: The state of the handler:
- A READY state means that the service handler can accept new connections.
- A BLOCKED state means that the service handler cannot accept new connections.
Following this, additional information about the service handler displays, such as whether the service handler is a dispatcher, a local dedicated server, or a remote dedicated server on another node
>>>http://download-west.oracle.com/docs/cd/B19306_01/network.102/b14212/listenercfg.htm#sthref1060

SCCM 2012 SP1 CU4 migrated DP shows package status "unknown"

I have a SCCM 2012 SP1 CU4 environment and have shared SCCM 2007 distribution points.
Today I migrated one of the DP's which seems to work well.
However all my packages shows now the status "unknown" for this migrated DP.
This is a problem which should be fixed in CU4 according to the CU4 description. But it is not :-(
Any idea how to solve this ? R2 install ?

Some additional information:
I noticed that the package sources are still available at the "old" ditribution point share abd not on the new sccm 2012 distribution point share. When performing actions described in step 3 below the package becomes available on the distribution point
share......then i guess i can remove the content from the "old" distribution point share ????
I noticed that when a package got the status "unknown" for de migrated DP the following action fix the problem:
--> i remove the DP from the package and immediately add it again, the package status becomes "Successful".....hummm....ok....maybe a script could be created for this
I noticed that when a package got the status "unknown" and the package is also located on the "distribution point share" then following will fix the issue:
--> edit the package and remove the migrated DP and remove the checkbox for string on the distribution point share. Then add the DP again, click Apply and then set the checkbox for storing on the distribution point share and Apply again. Then wait and package
will become available Successful and the package will become available on the distribution point share
But i have 800 packages and 50 to be migrated DP's.....this is not a solution....but what is ????
Any help, ideas, tips, hints, recommendations ?
My overal thoughts are that migrating of a SCCM 2007 DP is not really working at all !!!!!
Or does someone has other experience with e.g. R2 installed ? If so then I will upgrade first...

Command for replication status

Sorry I have so many questions.
This question regarding the status of replication. In 4.16, I can run a command to get the replication status that saying idle[in sync]. So I know replication is working fine. But 5.1, it seems does not have such words in replication status. From GUI, it just say last update message. How can I know the replication status by command line instead of GUI? Just by the last update message " ...update successfully", can I tell the replication works? What about if nothing need to update and one of the master down? For such scenerio, the replicaion should be down. How an tell it by a command line?
Thanks
Iris

I believe there is a perl script in the iDS 5.1 resource kit called replcheck.pl (?) that will monitor and update replication status.
http://wwws.sun.com/software/download/products/sunone/3dee7c94.html

CUCM Database Replication Status MIB

Hi Guys,
Can you please help me whether we could monitor CCM database replication status through SNMP MIB or OID..
Also please guide me in how to configure SNMP traps for the MIBS??
Regards,
Indrajith PC

Hi,
please take a look at the CUCM serviceability guide:
http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/service/9_0/admin/CUCM_BK_C136FE37_00_cisco-unified-serviceability-administration-90/CUCM_BK_C136FE37_00_cisco-unified-serviceability-administration-guide_preface_00.html
I'm afraid there's no trap generated when DB replication issues occur, so you might want to do periodic polling.
The above referenced document contains some basic information which MIB's may be interesting to you and how to get them.
Personally, I would download and register them all, and then just walk the whole tree and cherrypick ;-)
G.

Status UNKNOWN

Hi,
on 9i when I launch :
lsnrctl start
I have :
Service "MYDB" has 1 instance(s).
Instance "MYDB", status UNKNOWN, has 1 handler(s) for this service...
The command completed successfully
And I can not connect to DB in sqlplus as sysdba, it hangs up ?
What is the probleme ?
Any idea.

These errors (already in use) could be due to listener already started.
What does lsnrctl stat say? (you'll see if listener is running then)
The UNKNOWN status is probably unrelated and comes from a statically configured service. Found this in the Net Services Admin guide. (look at the end of table 12-2)
What is the real problem? What happens when you do
$ sqlplus "/ as sysdba"

Adf input file - connection to the server has failed(status=unknown)

We are using input file component to upload an excel file and read it. Sometimes we are getting error - " A Connection to the server has failed. (status=unknown) " when we click on browse and add the file. We are getting this error when we just add the file. We are not doing any operation while adding the file. After the file is added, we have a submit button to do post operations on file. But we are getting this error immediately after we add the file. JDeveloper version 11.1.1.5.0.
Any inputs will help us.
Edited by: adf_forum on May 23, 2013 5:24 PM

Hi,
there must be a stack trace in the log files that gives you more information about this. Chances are the browser closes the socket connection, which you can verify by using another browser and avoiding e.g. VPN connect for testing. Another test to perform is to try 11.1.1.7 and see if this works for the use case in case you sit on a known and already fixed problem
Frank

Replication Status UNKNOWN?

Similar Messages

Maybe you are looking for