Not able to connect as sys

I want to access the database through network. I was able to conect as scott. but when i tried to connect as sys this gives me error "connection as sys should be as sysdba or sysoper".
Syntax
sqlplus "sys/abc@xxx"
Please help me to solve this problem.
Thanks

The parameter is required but not enough. Have you already created your password file? Are you sure your password file is already at its position:
$ORACLE_HOME/dbs/orapw$ORACLE_SID   (unix)
%ORACLE_HOME%\database\PWD$ORACLE_SID.ORAOtherwise you'll have to create one, using the orapwd utility:
OS>orapwd
Usage: orapwd file=<fname> password=<password> entries=<users> force=<y/n>
where
    file - name of password file (mand),
    password - password for SYS (mand),
    entries - maximum number of distinct DBA and     force - whether to overwrite existing file (opt),
OPERs (opt),
There are no spaces around the equal-to (=) character.

Similar Messages

Enterprise Manager is not able to connect to the database instance. Open??

Hello there,
After I installed oracle database and tried to start Enterprise Manager, I got the message:
Enterprise Manager is not able to connect to the database instance.
All statuses are OK (green and up) except database instance. It is also green and up but open. (Details: The instance is open.)
Can anyone help me about it?
I use Windows XP x64 with all patches installed. Oracle database R11g x64.
I tried with different database versions and different machines and different OS and loopback adapter and... my EM still want to log in.
I can log in with sqlplus. It accepts any pass for sys (as sysdba). Why?
My log files are available here: http://195.66.185.187/log.zip

You are using a bequeath connection when logging in with SQL*Plus on the server so the password is not validated.
Log in using SQL*Plus this way:
sqlplus /nolog
followed by
conn sys@<service_name> AS SYSDBA
and provide the correct password
My guess it it will fail.
If so then you need to use the correct password and if you don't know what it is set it when logged on as SYS.

Not able to connect as sysoper in sql*plus

Friends,
Why i am not able to connect as sysoper?
OS: win 2000
Oracle db: oracle 9i
tool is sql*plus
SQL> connect / as sysdba
Connected.
SQL> show user
USER is "SYS"
SQL> connect / as sysoper
ERROR:
ORA-01031: insufficient privileges
Warning: You are no longer connected to ORACLE.
SQL>
where i am making mistake?
Thanks
Sathyguy

In Linux i know to add.
But in windows....i dont know.
could you please tell me how to add this group.
Actually we will login to the os using our company name as a group.

Not able to connect to oracle directly

os : AIX ch5dlfp089 1 6 000B4A22D900
oracle : 11.2.0.1.0
Issue : created oracle db using dbca (gui). Db created successfully
When I checked recently using putty to check the db health. I am able to see smon and orcl is running well using
ps -eaf | grep orcl.
How ever when I am trying to connect the db using sqlplus prompt. It is showing idle instance.
$ sqlplus "/ as sysdba"
SQL*Plus: Release 11.2.0.1.0 Production on Mon Oct 18 00:52:08 2010
Copyright (c) 1982, 2009, Oracle. All rights reserved.
Connected to an idle instance.
SQL> exit
oratab entry shows ok
orcl:/home/oracle/app/oracle/product/11.2.0/dbhome_1:
CHECKED BASIC ENV. variables values
$ echo $ORACLE_SID
orcl
$ echo $ORACLE_HOME
/home/oracle/app/oracle/product/11.2.0/dbhome_1/
profile shows as follows
$ cat .profile
PATH=/usr/bin:/etc:/usr/sbin:/usr/ucb:$HOME/bin:/usr/bin/X11:/sbin:.
export PATH
if [ -s "$MAIL" ] # This is at Shell startup. In normal
then echo "$MAILMSG" # operation, the Shell checks
fi # periodically.
ORACLE_SID=orcl
export ORACLE_SID
ORACLE_HOME=/home/oracle/app/oracle/product/11.2.0/dbhome_1/
export ORACLE_HOME
LIBPATH=$ORACLE_HOME/lib:$LIBPATH
export LIBPATH
PATH=$ORACLE_HOME/bin:$PATH
export PATH
However I am able to connect to db using tns
$ sqlplus "sys/Oracle123@orcl as sysdba"
Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
SQL> EXIT
Question : what could be the reason I am not able to connect the db directly ? without tns ?
Any mistake could have happend or any restriction could have set for this access ?

I already tested that ORCL
$ echo $ORACLE_SID
orcl
$ export ORACLE_SID=ORCL
$ echo $ORACLE_SID
ORCL
$ sqlplus "/ as sysdba"
SQL*Plus: Release 11.2.0.1.0 Production on Mon Oct 18 01:08:03 2010
Copyright (c) 1982, 2009, Oracle. All rights reserved.
Connected to an idle instance.
LISTNER
$ lsnrctl status
LSNRCTL for IBM/AIX RISC System/6000: Version 11.2.0.1.0 - Production on 18-OCT-2010 01:09:00
Copyright (c) 1991, 2009, Oracle. All rights reserved.
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC1521)))
STATUS of the LISTENER
Alias LISTENER
Version TNSLSNR for IBM/AIX RISC System/6000: Version 11.2.0.1.0 - Production
Start Date 14-OCT-2010 00:14:39
Uptime 4 days 0 hr. 54 min. 22 sec
Trace Level off
Security ON: Local OS Authentication
SNMP ON
Listener Parameter File /home/oracle/app/oracle/product/11.2.0/dbhome_1/network/admin/listener.ora
Listener Log File /home/oracle/app/oracle/diag/tnslsnr/ch5dlfp089/listener/alert/log.xml
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC1521)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=ch5dlfp089.in.ibm.com)(PORT=1521)))
Services Summary...
Service "orcl.in.ibm.com" has 1 instance(s).
Instance "orcl", status READY, has 1 handler(s) for this service...
Service "orclXDB.in.ibm.com" has 1 instance(s).
Instance "orcl", status READY, has 1 handler(s) for this service...
The command completed successfully
$
TNS SHOWS
$ tnsping orcl
TNS Ping Utility for IBM/AIX RISC System/6000: Version 11.2.0.1.0 - Production on 18-OCT-2010 01:09:51
Copyright (c) 1997, 2009, Oracle. All rights reserved.
Used parameter files:
/home/oracle/app/oracle/product/11.2.0/dbhome_1/network/admin/sqlnet.ora
Used TNSNAMES adapter to resolve the alias
Attempting to contact (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = ch5dlfp089.in.ibm.com)(PORT = 1521)) (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME = orcl.in.ibm.com)))
OK (30 msec)
$
TNSNAMES ENTRY
$ cat tnsnames.ora
# tnsnames.ora Network Configuration File: /home/oracle/app/oracle/product/11.2.0/dbhome_1/network/admin/tnsnames.ora
# Generated by Oracle configuration tools.
orcl =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = ch5dlfp089.in.ibm.com)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = orcl.in.ibm.com)
)

Not able to connect after changing the password using ALTER VALUES clause

Hi,
Just now John explained about VALUES clause in below thread.
Expired Status
I created a new account called SURI and tried to use the user account HR's password using VALUES clause. I was able to alter the password but not able to connect SURI with hr password.
Please see the version details below. And the SQL statements which I have tried.
SQL*Plus: Release 10.2.0.1.0 - Production on Mon Aug 13 18:44:50 2012
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Enter user-name: sys as sysdba
Enter password:
Connected to:
Oracle Database 10g Express Edition Release 10.2.0.1.0 - Production
SQL> SELECT password
2 FROM dba_users
3 WHERE username = 'HR';
PASSWORD
4C6D73C3E8B0F0DA
SQL> ALTER USER SURI IDENTIFIED BY VALUES '4C6D73C3E8B0F0DA';
User altered.
SQL> SELECT password
2 FROM dba_users
3 WHERE username='SURI';
PASSWORD
4C6D73C3E8B0F0DA
SQL> conn suri/hr -- HR account's password is hr only
ERROR:
ORA-01017: invalid username/password; logon denied
Warning: You are no longer connected to ORACLE.
SQL>Thanks,
Suri

Suri wrote:
Hi,
Just now John explained about VALUES clause in below thread.
Expired Status
I created a new account called SURI and tried to use the user account HR's password using VALUES clause. I was able to alter the password but not able to connect SURI with hr password.
Please see the version details below. And the SQL statements which I have tried.
SQL*Plus: Release 10.2.0.1.0 - Production on Mon Aug 13 18:44:50 2012
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Enter user-name: sys as sysdba
Enter password:
Connected to:
Oracle Database 10g Express Edition Release 10.2.0.1.0 - Production
SQL> SELECT password
2 FROM dba_users
3 WHERE username = 'HR';
PASSWORD
4C6D73C3E8B0F0DA
SQL> ALTER USER SURI IDENTIFIED BY VALUES '4C6D73C3E8B0F0DA';
User altered.
SQL> SELECT password
2 FROM dba_users
3 WHERE username='SURI';
PASSWORD
4C6D73C3E8B0F0DA
SQL> conn suri/hr -- HR account's password is hr only
ERROR:
ORA-01017: invalid username/password; logon denied
Warning: You are no longer connected to ORACLE.
SQL>Thanks,
SuriYou can only do it for the same user, as the password is a hashed value that includes the username as part of the hashing (It's either the username or some internal object id or something). So using the hashed value against another user won't work.

Not able to connect to the database

I have installed oracle9i in my machine.
i have moved control files from one location to other and changed the locations in the init.ora and restated the database from services, but i am able to connect to only sys user and i am not able to connect to any other user.
can anybody please help me to solve this problem.
Thanks and regards,
Sateesh Kota

Hi joe,
thanks for ur reply.
actually my database is running on SPFILE.
i have changed the init file and i have tried to start the database. that is why it was giving me problem.
i am able to start the database but i am able to connect to users. only as sysdba i am able to connect.
then i have solved it by startng with pfile and made spfile again and i have shutted down and just started with spfile. then it is running fine now.
thanks for ur reply once again.
what u mean by "bouncing the DB" can u please explain that
Sateesh

In 2 node RAC. After shutting down database not able to connect.

I have 2 node Oracle 10g RAC (RAC-1 and RAC-2) on Windows 2003 Server.
After shutting down instance on RAC-2
I am not able to connect to database from any node.
I did this on RAC-2 :
SQL>shutdown immediate;
Database went down smoothly.
SQL>conn sys/oracle@rac as sysdba
ERROR:
ORA-12514: TNS:listener does not currnetly know of services requested in connect descriptor.
My first node is running fine but I am not able to connect to database from first node or from client.
Any suggestion???
Regards:
Sushil

One question I want to ask, what should be the Listener Services startup mode in RAC? MANUAL or AUTOMATIC???Ideally, if you are instances and other oracle resources are set to autostart then there is no reason for you to set the listener to MANUAL. You may like to change it to AUTOMATIC so that on reboot it comes up without manual intervention.

Enterprise Manager not able to connect to the Database Instance

After logging into the OEM as a SYS user , I was able to mount the database . The Database status shown to me as below,
Listener - up
Agent Connection to the Instance - unavailable
Database instance- down - message - Enterprise Manager is not able to connect to the database instance.
After that I tried to connect to the database through sql developer , I was able to connect using connection for the SYS user and able to run the queries .d
So How can I be able to connect to the Database Instance using OEM ?
Please suggest me what to do or what to check ...
Your help will be appreciated...

965493 wrote:
emoms error code as below..
2012-10-17 02:22:35,703 [shutdownHookThread] ERROR em.notification unregisterOMS.1438 - Error unregistering: Listener refused the connection with the following error:
ORA-12514, TNS:listener does not currently know of service requested in connect descriptor
The Connection descriptor used by the client was:
(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=localhost)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=orcl)))
java.sql.SQLException: Listener refused the connection with the following error:
ORA-12514, TNS:listener does not currently know of service requested in connect descriptor
The Connection descriptor used by the client was:
(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=localhost)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=orcl)))ORA-12514 ALWAYS only occurs due to a problem on DB Server system.
One cause of this problem is when the Oracle database is down & needs to be started.
A remote client send a request to the Listener asking to be connected to a specific service.
If/when the listener does not know anything about that service, the listener responds with ORA-12514
post results from the following two OS commands:
lsnrctl status
lsnrctl service
Since every connection request to the listener gets logged, listener.log file will contain a line with 12514 as status code.
This line contains valuable debugging details. So post this line & surrounding lines.
for additional debugging suggestions read the URL below:
http://edstevensdba.wordpress.com/2011/03/19/ora-12514/

10g Enterprise Manager is not able to connect to the database instance

I am running a Oracle 10g database in Solaris 10 server. When i am trying to connect to the enterprise manager it says Enterprise Manager is not able to connect to the database instance.
The database instance is open,the listener is up and the agent connection also says that it succeeded.
The server houses two 10g databases and the EM was working properly till yesterday. Kindly Help.
Thanks in advance.
Ram

Hi,
The EM is started and if i give emctl status dbconsole
-bash-3.00$ emctl status dbconsole
Oracle Enterprise Manager 10g Database Control Release 10.2.0.3.0
Copyright (c) 1996, 2006 Oracle Corporation. All rights reserved.
http://gladiator:1158/em/console/aboutApplication
Oracle Enterprise Manager 10g is running
Logs are generated in directory /db8/ora10gr2/product/10.2.0/Db_4/gladiator_TROY/sysman/log
it says that the EM is running. But when i am trying to access the URL it is in IE it says Page cannot be displayed what could be the problem for this???
Thanks in advance.
Ram

Reporting Services not able to connect with sharepoint

HI
We have a Sql server instance where we are not able to install reporting services, so what we have done is we have created one more sql server instance on the same server with reporting services.
When we configured reporting services in sharepoint integrated mode and try to connect that web service url in sharepoint we are getting an error in sharepoint central administartion that not able to connect to the reporting services.
Request you to throw some light on the same.
Thanks
Geeth If you feel that the answer which i gave you is Helpful please select it as Answer/helpful.

Hi Geeth,
Based on the limited information, I am not very clearly about you issue. In order to solve the problem more efficiently, I need to clarify some information. Could you post more detail information about “try to connect that web service url in sharepoint we
are getting an error in sharepoint central administartion”? For example, the detail steps about the action, the screenshot of the action, and what error message you received. I’m not sure which step are you trying to do. And could you tell me the edition of
your SQL Server and SharePoint? It is benefit for us to do further analysis.
References:
2008 R2:
http://technet.microsoft.com/en-us/library/bb283190(v=sql.105).aspx
http://sharepointtaskmaster.blogspot.in/2010/11/intergration-reporting-service-with.html
http://technet.microsoft.com/en-us/library/bb326213(v=sql.105).aspx
2012:
http://technet.microsoft.com/en-us/library/47efa72e-1735-4387-8485-f8994fb08c8c
http://denglishbi.wordpress.com/2011/07/22/configuring-sql-server-denali-reporting-services-sharepoint-2010-integration/
Hope this helps.
Thanks,
Katherine Xiong
Katherine Xiong
TechNet Community Support

Not able to connect CRM Online to PowerBI

Not able to connect CRM Online to PowerBI, Please let me know if you have an idea to resolve this issue.
oops, something went wrong
Failed to update model parameters
Activity Id59a2a854-8e34-6636-0679-3d2e245d2241
Request Id9b7fa606-324e-4ec8-495f-13f91d03bc54
Error Code400
TimeWed Mar 18 2015 21:24:18 GMT-0400 (Eastern Daylight Time)
Version11.0.9165.945
Cluster URIhttps://wabi-south-east-asia-redirect.analysis.windows.net

Hi Kiran
Please chcek the Note 1359600-MDM stopped communicating after upgrading to 7.1.03 from SAP NOTES.
https://websmp230.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=1359600
SAP Note Description:
Summary
Symptom
MDM components stopped communicating after upgrading to 7.1.03
Other terms
TCP ports, Firewall, connection, network, SP03, SP3, 7.1
Reason and Prerequisites
Starting from version 7.1.03 the MDM suite is using different TCP ports for its operations. The change was in order to be compliant with the Internet Authority for Numbering Assignment. Port numbers changed as follows:
Application Old Port # New Port #
MDS 20005 59950
MDLS 20008 59650
MDIS 20009 59750
MDSS 20010 59850
If firewalls were configured to allow MDM's communication throughout the landscape, they actually might prevent (depending on their rules table) the communication after an upgrade to MDM suite starting at version 7.1.03 and higher.
Solution
Revise the firewall rules such that they will allow the communication according to the changes described above.
In order to check that the ports are allowed to pass trough the firewall a telnet test could be done like so:
1) Open a terminal window (on UNIX) or a command window (on Windows) on the same machine which hosts the application which tries to connect, and issue the following command:
telnet <MDM server host name or IP address> <TCP port to test>
2) If no error response is received than it means that the TCP port is allowed to go trough.
3) Repeat steps 1,2 for all the other ports need by the application.
Thanks
Sowseel
Edited by: sowseel pasumarthi on Jan 18, 2011 6:36 AM

Not able to connect N70 to pc(xp) using ca-53 cabl...

Not able to connect N70 to pc(xp) using ca-53 cable
hi i am having this trouble from a year... i am unable to connect my phone n70 using cable to my pc,.,. even after installing all drivers n pc suite n havin it reinstalled also n again doin d same process.. its not getting detected at all.. please help me out... pleaseeee..been tryin 4m a year..nevr checkd des forumss.. hopin som bdy ll help ,me out.. !!!. !!!!

The DKU-2 cable is no longer supported and so cannot be guaranteed to be compatible with current PC Suites, you should be using either your current CA-53 or the CA-70.
Have you had the chance to connect any other phone with the PC using this cable? This would test if thr cable itself might be faulty.
Otherwise remove PC Suite, PC Connectivitiy Solution and Connectivity Cable Drivers from control panel, run the PC Suite Cleaner program that you can get from the PC Suite support pages on the web site, then reinstall everything.

Not able to connect to wifi wpa2 networks in lenovo vibe x2

Not able to connect to wifi wpa2 networks in lenovo vibe x2. It displayed saved.but not connecting. It connects to open and WEP wifi networks. Please help

Are you trying to connect to a 2.4GHz or a 5GHz network?
What encryption is your router set to use : AES,TKIP/AES,..?
Have you tried to unplug the router from the power source for 2-3 minutes->Plug it back in-> Wait until it establishes an Internet connection-> Try to recreate the phone connection.
Did someone help you today? Press the star on the left to thank them with a Kudo!
If you find a post helpful and it answers your question, please mark it as ''ACCEPT AS SOLUTION"!
Unsolicited PM's will not be answered! ....Please post your question/s in the appropriate forum board.
English Community Deutsche Community Comunidad en Español Русскоязычное Сообщество

Not able to connect to a queue under a foreign server.

Not able to connect to a queue under a foreign server.
I'm using WebLogic Server Version: 10.3.3.0. The foreign server is running, and can be pinged from this local server. Also the port where queue resides on foreign server, can be accessed through the my local server.
OS used is AIX 6.0 on both servers.
Tried restarting the local server but nothing helps. Same error continues.
HAS ANYBODY FACED THIS PROBLEM? WHAT IS THE CAUSE AND SOLUTION FOR THIS?
It throws following errors:
<Jun 25, 2012 12:14:15 AM GMT+06:00> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: NotificationQueueAnonymousWaiter is unable to connect to the JMS destination: NOTIFY_QUEUE. The Error was:
javax.naming.NoInitialContextException: Failed to create InitialContext using factory specified in hashtable [Root exception is java.lang.ClassCastException: Expected RemoteException, RuntimeException, or Error but received: 'java.io.IOException: RJVM has already been shutdown']
     at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:247)
     at javax.naming.InitialContext.initializeDefaultInitCtx(InitialContext.java:318)
     at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:348)
     at javax.naming.InitialContext.internalInit(InitialContext.java:286)
     at javax.naming.InitialContext.<init>(InitialContext.java:211)
     at weblogic.deployment.jms.ForeignOpaqueReference.getReferent(ForeignOpaqueReference.java:179)
     at weblogic.jndi.internal.WLNamingManager.getObjectInstance(WLNamingManager.java:96)
     at weblogic.jndi.internal.ServerNamingNode.resolveObject(ServerNamingNode.java:377)
     at weblogic.jndi.internal.BasicNamingNode.resolveObject(BasicNamingNode.java:856)
     at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:209)
     at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:254)
     at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:393)
     at javax.naming.InitialContext.lookup(InitialContext.java:436)
     at weblogic.jms.common.CDS$2.run(CDS.java:503)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
     at weblogic.jms.common.CrossDomainSecurityManager.runAs(CrossDomainSecurityManager.java:130)
     at weblogic.jms.common.CDS.lookupDestination(CDS.java:497)
     at weblogic.jms.common.CDS.getDDMembershipInformation(CDS.java:276)
     at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.createMDManagers(MessageDrivenBeanInfoImpl.java:1455)
     at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.activate(MessageDrivenBeanInfoImpl.java:1252)
     at weblogic.ejb.container.deployer.EJBDeployer.activate(EJBDeployer.java:1320)
     at weblogic.ejb.container.deployer.EJBModule.activate(EJBModule.java:493)
     at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:227)
     at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:531)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:165)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:157)
     at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:1267)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
     at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:409)
     at weblogic.application.internal.SingleModuleDeployment.activate(SingleModuleDeployment.java:43)
     at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
     at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
     at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116)
     at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844)
     at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440)
     at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:13)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:68)
     at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused by: java.lang.ClassCastException: Expected RemoteException, RuntimeException, or Error but received: 'java.io.IOException: RJVM has already been shutdown'
     at weblogic.common.internal.BootServicesStub.getMsg(BootServicesStub.java:34)
     at weblogic.common.internal.BootServicesStub.authenticate(BootServicesStub.java:54)
     at weblogic.security.acl.internal.RemoteAuthenticate.authenticate(RemoteAuthenticate.java:90)
     at weblogic.jndi.WLInitialContextFactoryDelegate.authenticateRemotely(WLInitialContextFactoryDelegate.java:746)
     at weblogic.jndi.WLInitialContextFactoryDelegate.pushSubject(WLInitialContextFactoryDelegate.java:678)
     at weblogic.jndi.WLInitialContextFactoryDelegate.newContext(WLInitialContextFactoryDelegate.java:469)
     at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:376)
     at weblogic.jndi.Environment.getContext(Environment.java:315)
     at weblogic.jndi.Environment.getContext(Environment.java:285)
     at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:117)
     at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:239)
     ... 46 more
>
<Jun 25, 2012 12:14:15 AM GMT+06:00> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: NotificationQueueAnonymousWaiter is unable to connect to the JMS destination: NOTIFY_QUEUE. The Error was:
Can not get destination information. The destination JNDI name is NOTIFY_QUEUE, the provider URL is null>
<Jun 25, 2012 12:14:45 AM GMT+06:00> <Error> <Common> <BEA-000621> <Expected RemoteException, RuntimeException, or Error
java.io.IOException: RJVM has already been shutdown
java.io.IOException: RJVM has already been shutdown
     at weblogic.rjvm.RJVMImpl.addPendingResponse(RJVMImpl.java:511)
     at weblogic.rjvm.RJVMImpl.send(RJVMImpl.java:898)
     at weblogic.rjvm.MsgAbbrevOutputStream.flushAndSend(MsgAbbrevOutputStream.java:394)
     at weblogic.rjvm.MsgAbbrevOutputStream.sendRecv(MsgAbbrevOutputStream.java:424)
     at weblogic.common.internal.BootServicesStub.authenticate(BootServicesStub.java:54)
     Truncated. see log file for complete stacktrace
>
<Jun 25, 2012 12:15:03 AM GMT+06:00> <Error> <Common> <BEA-000621> <Expected RemoteException, RuntimeException, or Error
java.io.IOException: RJVM has already been shutdown
java.io.IOException: RJVM has already been shutdown
     at weblogic.rjvm.RJVMImpl.addPendingResponse(RJVMImpl.java:511)
     at weblogic.rjvm.RJVMImpl.send(RJVMImpl.java:898)
     at weblogic.rjvm.MsgAbbrevOutputStream.flushAndSend(MsgAbbrevOutputStream.java:394)
     at weblogic.rjvm.MsgAbbrevOutputStream.sendRecv(MsgAbbrevOutputStream.java:424)
     at weblogic.common.internal.BootServicesStub.authenticate(BootServicesStub.java:54)
     Truncated. see log file for complete stacktrace
>
<Jun 25, 2012 12:15:25 AM GMT+06:00> <Error> <Common> <BEA-000621> <Expected RemoteException, RuntimeException, or Error
java.io.IOException: RJVM has already been shutdown
java.io.IOException: RJVM has already been shutdown
     at weblogic.rjvm.RJVMImpl.addPendingResponse(RJVMImpl.java:511)
     at weblogic.rjvm.RJVMImpl.send(RJVMImpl.java:898)
     at weblogic.rjvm.MsgAbbrevOutputStream.flushAndSend(MsgAbbrevOutputStream.java:394)
     at weblogic.rjvm.MsgAbbrevOutputStream.sendRecv(MsgAbbrevOutputStream.java:424)
     at weblogic.common.internal.BootServicesStub.authenticate(BootServicesStub.java:54)
     Truncated. see log file for complete stacktrace
>
<Jun 25, 2012 12:15:35 AM GMT+06:00> <Error> <Common> <BEA-000621> <Expected RemoteException, RuntimeException, or Error
java.io.IOException: RJVM has already been shutdown
java.io.IOException: RJVM has already been shutdown
     at weblogic.rjvm.RJVMImpl.addPendingResponse(RJVMImpl.java:511)
     at weblogic.rjvm.RJVMImpl.send(RJVMImpl.java:898)
     at weblogic.rjvm.MsgAbbrevOutputStream.flushAndSend(MsgAbbrevOutputStream.java:394)
     at weblogic.rjvm.MsgAbbrevOutputStream.sendRecv(MsgAbbrevOutputStream.java:424)
     at weblogic.common.internal.BootServicesStub.authenticate(BootServicesStub.java:54)
     Truncated. see log file for complete stacktrace
>
<Jun 25, 2012 12:15:43 AM GMT+06:00> <Error> <Common> <BEA-000621> <Expected RemoteException, RuntimeException, or Error
java.io.IOException: RJVM has already been shutdown
java.io.IOException: RJVM has already been shutdown
     at weblogic.rjvm.RJVMImpl.addPendingResponse(RJVMImpl.java:511)
     at weblogic.rjvm.RJVMImpl.send(RJVMImpl.java:898)
     at weblogic.rjvm.MsgAbbrevOutputStream.flushAndSend(MsgAbbrevOutputStream.java:394)
     at weblogic.rjvm.MsgAbbrevOutputStream.sendRecv(MsgAbbrevOutputStream.java:424)
     at weblogic.common.internal.BootServicesStub.authenticate(BootServicesStub.java:54)
     Truncated. see log file for complete stacktrace
>
<Jun 25, 2012 12:20:53 AM GMT+06:00> <Error> <Common> <BEA-000621> <Expected RemoteException, RuntimeException, or Error
java.io.IOException: RJVM has already been shutdown
java.io.IOException: RJVM has already been shutdown
     at weblogic.rjvm.RJVMImpl.addPendingResponse(RJVMImpl.java:511)
     at weblogic.rjvm.RJVMImpl.send(RJVMImpl.java:898)
     at weblogic.rjvm.MsgAbbrevOutputStream.flushAndSend(MsgAbbrevOutputStream.java:394)
     at weblogic.rjvm.MsgAbbrevOutputStream.sendRecv(MsgAbbrevOutputStream.java:424)
     at weblogic.common.internal.BootServicesStub.authenticate(BootServicesStub.java:54)
     Truncated. see log file for complete stacktrace
>
<Jun 25, 2012 12:24:16 AM GMT+06:00> <Error> <Common> <BEA-000621> <Expected RemoteException, RuntimeException, or Error
java.io.IOException: RJVM has already been shutdown
java.io.IOException: RJVM has already been shutdown
     at weblogic.rjvm.RJVMImpl.addPendingResponse(RJVMImpl.java:511)
     at weblogic.rjvm.RJVMImpl.send(RJVMImpl.java:898)
     at weblogic.rjvm.MsgAbbrevOutputStream.flushAndSend(MsgAbbrevOutputStream.java:394)
     at weblogic.rjvm.MsgAbbrevOutputStream.sendRecv(MsgAbbrevOutputStream.java:424)
     at weblogic.common.internal.BootServicesStub.authenticate(BootServicesStub.java:54)
     Truncated. see log file for complete stacktrace
Edited by: 942523 on Jun 24, 2012 11:38 PM

Thanks René van Wijk for the reply.
I have a foreign server created in my local server, where i have already given the provider URL. This foreign server has the one queue and one queue connection factory under it to which I'm referring to.
Under JNDI tree i noticed this, for the queue(NOTIFY_QUEUE) i'm trying to read from one of the EJB:
This page displays details about this bound object.
Failed to create InitialContext using factory specified in hashtable
Also,etc/hosts has already these IP entries. Even after hardcoding the provider URL its throwing following:
<Jun 25, 2012 3:01:31 AM GMT+06:00> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: NotificationQueueAnonymousWaiter is unable to connect to the JMS destination: NOTIFY_QUEUE. The Error was:
javax.naming.CommunicationException [Root exception is weblogic.rjvm.PeerGoneException: ; nested exception is:
     java.io.EOFException]
     at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:74)
     at weblogic.jndi.internal.WLContextImpl.translateException(WLContextImpl.java:452)
     at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:408)
     at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:393)
     at javax.naming.InitialContext.lookup(InitialContext.java:436)
     at weblogic.jms.common.CDS$2.run(CDS.java:503)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
     at weblogic.jms.common.CrossDomainSecurityManager.runAs(CrossDomainSecurityManager.java:130)
     at weblogic.jms.common.CDS.lookupDestination(CDS.java:497)
     at weblogic.jms.common.CDS.getDDMembershipInformation(CDS.java:276)
     at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.createMDManagers(MessageDrivenBeanInfoImpl.java:1455)
     at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.activate(MessageDrivenBeanInfoImpl.java:1252)
     at weblogic.ejb.container.deployer.EJBDeployer.activate(EJBDeployer.java:1320)
     at weblogic.ejb.container.deployer.EJBModule.activate(EJBModule.java:493)
     at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:227)
     at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:531)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:165)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:157)
     at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:1267)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
     at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:409)
     at weblogic.application.internal.SingleModuleDeployment.activate(SingleModuleDeployment.java:43)
     at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
     at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
     at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116)
     at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844)
     at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440)
     at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:13)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:68)
     at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused by: weblogic.rjvm.PeerGoneException: ; nested exception is:
     java.io.EOFException
     at weblogic.rjvm.ResponseImpl.unmarshalReturn(ResponseImpl.java:234)
     at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:348)
     at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:259)
     at weblogic.jndi.internal.ServerNamingNode_1033_WLStub.lookup(Unknown Source)
     at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:405)
     ... 36 more
Caused by: java.io.EOFException
     at weblogic.rjvm.t3.MuxableSocketT3.endOfStream(MuxableSocketT3.java:338)
     at weblogic.socket.SocketMuxer.deliverExceptionAndCleanup(SocketMuxer.java:768)
     at weblogic.socket.SocketMuxer.deliverEndOfStream(SocketMuxer.java:702)
     at weblogic.socket.SocketMuxer.readReadySocketOnce(SocketMuxer.java:890)
     at weblogic.socket.SocketMuxer.readReadySocket(SocketMuxer.java:840)
     at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:130)
     at weblogic.socket.SocketReaderRequest.run(SocketReaderRequest.java:29)
     at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:42)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:145)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:117)
>
<Jun 25, 2012 3:01:31 AM GMT+06:00> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: NotificationQueueAnonymousWaiter is unable to connect to the JMS destination: NOTIFY_QUEUE. The Error was:
Can not get destination information. The destination JNDI name is NOTIFY_QUEUE, the provider URL is t3://10.52.50.51:7002>
Let me know if any other thing i'm missing or it can be something else like network or some other issue.

IPad 2 - I am not able to connect my iPad 2 to my tv anymore using AV adapter.

What is wrong with my iPad 2? I'm not able to conect my iPad to my proyector or tv anymore using AV adaptor. Is there something wrong with my iPad?
I tried it with my wife's iPad 2 and it was the same result. I was not able to connect her iPad to my TV. Niether TV or a proyector couldn't find the device.
Would you please help me? Your help will be well appreciated.

Sounds like the one common thing is the adapter. The cheaper, non apple branded ones tend to fail.
Try another adaptor before worrying about your ipad.

Not able to connect as sys

Similar Messages

Maybe you are looking for