Upgrade to MaxDB 7.8 fails due to -4008,Unknown user name/password

Hello,
I have a strange problem. I try to update a MaxDB 7.7 instance to 7.8.
I start ./DBUPDATE.SH:
INFORMATION : This program upgrades the SAP MaxDB database instance
Do you want to continue the upgrade [Y] :  Y
Check installation of C++ runtime
...execution 12:08:59
OK
IndepProgPath : /sapdb/programs
IndepDataPath : /sapdb/data
Please enter SAP MaxDB Name    [SID] :  J93
Please enter SAP System Name   [SID] :  J93
Please enter DBM User Name [control] :  control
Please enter DBM User Password       :
INSTROOT        : /sapdb/J93/db
Authorization successful
DB KERNEL       : 64-BIT
DB VERSION      : 7.7.04 Build 28
Database instance version supported
PrivateDataPath : NO
Check availability of SAP users
...execution 12:09:05
SAP System Administrator   : j93adm
SAP Database Administrator : sqdj93
OK
SAP VERSION     : -4008,Unknown user name/password combination
Please confirm the upgrade start [Y] :
Obviously the DBM user and password have been accepted.
Also I created the xuser entry according to SAP note 39439:
xuser -U DEFAULT -u SAPJ93DB,password -d J93 -S SAPR3 -n minbbn30 -t 0 -I 0 set
xuser list
XUSER Entry  1
Key           :DEFAULT
Username      :SAPJ93DB
UsernameUCS2  :S.A.P.J.9.3.D.B. . . . . . . . . . . . . . . . . . . . . . . . .
Password      :?????????
PasswordUCS2  :?????????
Long Password :?????????
Dbname        :J93
Nodename      :minbbn30
Sqlmode       :SAPR3
Cachelimit    :-1
Timeout       :0
Isolation     :0
Charset       :<unspecified>
I can successfully connect to the database with SAPJ93DB:
dbmcli -u control,password -d J93 sql_connect SAPJ93DB,password
OK
So why can't I simply upgrade this MaxDB instance? Is there any logfile of DBUPDATE.SH with more information available?
Regards,
Mark

Hi Mark,
this error can be ignored (see note 1353266, section IV "Errors during the upgrade").
Continue the upgrade by answering the question
SAP VERSION     : -4008,Unknown user name/password combination
Please confirm the upgrade start [Y] :
with Y.
Regards,
Steffen

Similar Messages

  • [-4008]: Unknown user name/password combination (MaxDB, Java)

    Hey,
    I'm having some troubles to connect to MaxDB using Java. I'm getting some error when I try to run my program.
    import java.sql.*;
    public class Hello
    public static void main(String[] args)
         throws ClassNotFoundException, SQLException
              String username = "DBM";
              String password = "azerty";
              String dbname = "SAPDB";
              Class.forName ("com.sap.dbtech.jdbc.DriverSapDB");
              Connection connection = DriverManager.getConnection("jdbc:sapdb:" + dbname, username, password);
    Exception in thread "main" com.sap.dbtech.jdbc.exceptions.DatabaseException: [-4008]: Unknown user name/password combination
         at com.sap.dbtech.jdbc.packet.ReplyPacket.createException(ReplyPacket.java:69)
         at com.sap.dbtech.jdbc.ConnectionSapDB.throwSQLError(ConnectionSapDB.java:768)
         at com.sap.dbtech.jdbc.ConnectionSapDB.execute(ConnectionSapDB.java:434)
         at com.sap.dbtech.jdbc.ConnectionSapDB.execute(ConnectionSapDB.java:325)
         at com.sap.dbtech.jdbc.ConnectionSapDB.doConnect(ConnectionSapDB.java:277)
         at com.sap.dbtech.jdbc.ConnectionSapDB.<init>(ConnectionSapDB.java:81)
         at com.sap.dbtech.jdbc.DriverSapDB.connect(DriverSapDB.java:184)
         at java.sql.DriverManager.getConnection(Unknown Source)
         at java.sql.DriverManager.getConnection(Unknown Source)
    I checked the User  and Password  with the GUI (Database manager) and everything works fine.
    I've also added the .jar in my Project Library.
    Any ideas ?
    Thanks

    Looking at your screen shot, it seems the database instance itself hasn't been correctly created because you lack permissions to do so. Subsequently, all your connection attempts basically fail because the database does not exists. I'm no real expert in SAP MaxDB administration on Microsoft Windows, but I read about System Error 5 once in a while earlier, have a look at  [http://www.syseva.com/2009/05/operating-system-error-5-5access-is-denied/|http://www.syseva.com/2009/05/operating-system-error-5-5access-is-denied/]. Overally, I suspect you don't have the permissions you need to have (operating system/file system -wise) in order to create the files belonging to a MaxDB instance (and/or required by the server and tools, such as the dbmsrv ... err file mentioned in the screen). Maybe you should check your system permissions? Are you administrator or member of the appropriate groups [http://maxdb.sap.com/doc/7_7/0e/218650d996419d91f6b234766eadd3/content.htm|http://maxdb.sap.com/doc/7_7/0e/218650d996419d91f6b234766eadd3/content.htm]? As pointed out, I'm no MaxDB/Windows expert, but this seems likely to be a problem as far as your screenshot is concerned.
    Cheers,
    Kristian

  • Can not connect to MaxDB 'Unknown user name/password combination' returned

    Hi,
         I try to make a connection from NWDS 7.2 to MaxDB. So i use the url as 'jdbc:sapdb://127.0.0.1:7210/CE1' to make a connection (by wizard of data source explorer in NWDS).
    I try to entry username and password as below :
    User : 'Administrator' , Pass : 'admin123'
    User : 'SAPJ2EDB' , Pass : 'admin123'
    User : 'superdba' , Pass : 'admin123'
    User : 'control' , Pass : 'admin123'
    So i always got
    com.sap.dbtech.jdbc.exceptions.jdbc40.SQLInvalidAuthorizationSpecException: [-4008]: Unknown user name/password combination
    returned
       I quite sure that 'admin123' is the password for MaxDB because when i try to uninstall the MaxDB it ask me to input password for 'superdba' and 'control'
    How should i do? I remember that when i installed the SAP CE7.2 i had entered just only one password.
    How can i reset the username and password or use default password?
    P.S i try to enter user and pass from this post MAXDB Server,Database,Username and pasword , but it still not work .
    Edited by: Thongie on Jul 14, 2011 2:48 PM

    Hi every one,
        I can solve it. I just restart DB and try agian.

  • The report server has encountered a configuration error. Logon failed for the unattended execution account. (rsServerConfigurationError) Log on failed. Ensure the user name and password are correct. (rsLogonFailed) Logon failure: unknown user name or bad

    The report server has encountered a configuration error. Logon failed for the unattended execution account. (rsServerConfigurationError)
    Log on failed. Ensure the user name and password are correct. (rsLogonFailed)
    Logon failure: unknown user name or bad password 
    am using Windows integrated security,version of my sql server 2008R2
    I have go throgh the different articuls, they have given different answers,
    So any one give me the  exact soluction for this problem,
    Using service account then i will get the soluction or what?
    pls help me out it is urgent based.
    Regards
    Thanks!

    Hi Ychinnari,
    I have tested on my local environment and can reproduce the issue, as
    Vaishu00547 mentioned that the issue can be caused by the Execution Account you have configured in the Reporting Services Configuration Manager is not correct, Please update the Username and Password and restart the reporting services.
    Please also find more details information about when to use the execution account, if possible,please also not specify this account:
    This account is used under special circumstances when other sources of credentials are not available:
    When the report server connects to a data source that does not require credentials. Examples of data sources that might not require credentials include XML documents and some client-side database applications.
    When the report server connects to another server to retrieve external image files or other resources that are referenced in a report.
    Execution Account (SSRS Native Mode)
    If you still have any problem, please feel free to ask.
    Regards
    Vicky Liu
    Vicky Liu
    TechNet Community Support

  • An account failed to log on unknown username or password. Causing Login audit failures

    I have a SBS11 Essentials server that is getting audit Failures over and over again. There computer account says it's the SBS11 server it's self.  It says unknown user name or bad password. I have checked for scheduled tasks, backup jobs, services and
    non of them are using any special user accounts.  I have used MS network monitor and can't find anything helpful to lead to the issue.  All computers in the network are running Windows 7.  The domain functional level is 2008 R2.
    I get a the 4768 event ID about a Kerberos event and then just after I get a Event ID 4625 account failure with Logon Type 3.  I have includes the events below.  I need to figure what is causing the audit failures as my GFI Test Hacker alert is
    catching it every morning.  Disabling the Test Hacker alert is not a option.  I have used Process Explorer also but can't seem to pin it down.  I also enabled Kerberos logging.
    http://support.microsoft.com/kb/262177?wa=wsignin1.0.  All event codes state its a unknown or no existing account but how do I stop it from happening?
    This is from the System Event log
    A Kerberos Error Message was received:
    on logon session TH.LOCAL\thsbs11e$
    Client Time:
    Server Time: 14:59:53.0000 3/4/2014 Z
    Error Code: 0x6 KDC_ERR_C_PRINCIPAL_UNKNOWN
    Extended Error:
    Client Realm:
    Client Name:
    Server Realm: TH.LOCAL
    Server Name: krbtgt/TH.LOCAL
    Target Name: krbtgt/[email protected]
    Error Text:
    File: e
    Line: 9fe
    Error Data is in record data.
    This is from the Security Event log
    A Kerberos authentication ticket (TGT) was requested.
    Account Information:
    Account Name: S-1-5-21-687067891-4024245798-968362083-1000
    Supplied Realm Name: TH.LOCAL
    User ID: NULL SID
    Service Information:
    Service Name: krbtgt/TH.LOCAL
    Service ID: NULL SID
    Network Information:
    Client Address: ::1
    Client Port: 0
    Additional Information:
    Ticket Options: 0x40810010
    Result Code: 0x6
    Ticket Encryption Type: 0xffffffff
    Pre-Authentication Type: -
    Certificate Information:
    Certificate Issuer Name:
    Certificate Serial Number:
    Certificate Thumbprint:
    Certificate information is only provided if a certificate was used for pre-authentication.
    Pre-authentication types, ticket options, encryption types and result codes are defined in RFC 4120.
    I then get teh following error in the next event
    An account failed to log on.
    Subject:
    Security ID: SYSTEM
    Account Name: THSBS11E$
    Account Domain: TH
    Logon ID: 0x3e7
    Logon Type: 3
    Account For Which Logon Failed:
    Security ID: NULL SID
    Account Name:
    Account Domain:
    Failure Information:
    Failure Reason: Unknown user name or bad password.
    Status: 0xc000006d
    Sub Status: 0xc0000064
    Process Information:
    Caller Process ID: 0x25c
    Caller Process Name: C:\Windows\System32\lsass.exe
    Network Information:
    Workstation Name: THSBS11E
    Source Network Address: -
    Source Port: -
    Detailed Authentication Information:
    Logon Process: Schannel
    Authentication Package: Kerberos
    Transited Services: -
    Package Name (NTLM only): -
    Key Length: 0
    This event is generated when a logon request fails. It is generated on the computer where access was attempted.
    The Subject fields indicate the account on the local system which requested the logon. This is most commonly a service such as the Server service, or a local process such as Winlogon.exe or Services.exe.
    The Logon Type field indicates the kind of logon that was requested. The most common types are 2 (interactive) and 3 (network).
    The Process Information fields indicate which account and process on the system requested the logon.
    The Network Information fields indicate where a remote logon request originated. Workstation name is not always available and may be left blank in some cases.
    The authentication information fields provide detailed information about this specific logon request.
    - Transited services indicate which intermediate services have participated in this logon request.
    - Package name indicates which sub-protocol was used among the NTLM protocols.
    - Key length indicates the length of the generated session key. This will be 0 if no session key was requested.

    Well I opened the case for him and he never followed up with Microsoft :-(
    It's a kerberos issue, we're told to ignore it.  Would you be willing to be patient and stubborn and work with CSS to at least understand what's going on better?  I can tell you it's normal with Essentials but not the exact technical reason it's
    happening.
    Unfortunately TechNet isn't coming back, sorry folks :-(

  • Downloaded music apps o.k.  Says login failed when I put in user and password. No trouble when getting any other apps.

    Downloaded music apps o.k.  Says login failed when I put in user and password. No trouble when getting any other apps.

    Sounds like you may have deleted something you shouldn't have. Boot to an OS X DVD or a bootable backup, and using Disk Utility, do a repair disk, and while there repair permissions. Disconnect any peripherals, and reboot. If you get the same startup behavior, do a safe boot, by holding the shift key down when booting. If that works, try a normal boot. If neither step helps, you may need to relaod your operating system.

  • I cannot conect to APP Store. I upgraded to IOS 8.3 and APP Store has not worked since. I am being asked to tipe my user name /password and nothing happens afterwards. No error messages either.

    I cannot connect to APP Store. I upgraded to IOS 8.3 and APP Store has not worked since. I am being asked to type my user name /password and nothing happens afterwards. No error messages either.

    hey the sever is down for the moment try again latter tonight... we have been attepting and i eveen went to the apple store third Street Primonade and alejadnro could not help me he said to try soon
    John

  • I updated from Snow Leorard to Moutain Lion and now my internet will not recognise  my password. All other comps use the network but my Mac upgraded Mac Mini keeps coming up with either 'timeout' or 'user or password not recognised' ...help!

    Hello all
    I upgraded from Snow Leopard to the latest Mountain Lion OS and now my Wifi will not work. When I try and insert the password to my Wifi network states either 'connection timed out' or 'password and/or user name not recognised' please help...!

    Take each of the following steps that you haven't already tried, until the problem is resolved.
    Step 1
    Restart the router. Many problems are solved that way.
    Step 2
    Change the name of the wireless network, if applicable, to eliminate any characters other than letters and digits. You do that on your router via its web page, if it's not an Apple device, or via AirPort Utility, if it is an Apple device.
    Step 3
    From the menu bar, select
     ▹ System Preferences... ▹ Network
    Click the Assist me button and select Assistant. Follow the prompts.
    Step 4
    Back up all data.
    Launch the Keychain Access application in any of the following ways:
    ☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
    ☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
    ☞ Open LaunchPad. Click Utilities, then Keychain Access in the icon grid.
    Enter the name of your wireless network in the search box. You should have one or more "AirPort network password" items with that name. Make a note of the name and password, then delete all the items. Quit Keychain Access. Turn Wi-Fi off and then back on. Reconnect to the network.
    Step 5
    You may need to change other settings on the router. See the guidelines linked below:
    Recommended settings for Wi-Fi routers and access points
    Potential sources of interference
    Step 6
    Make a note of all your settings for Wi-Fi in the Network preference pane, then delete the connection from the connection list and recreate it with the same settings. You do this by clicking the plus-sign icon below the connection list, and selecting Wi-Fi as the interface in the sheet that opens. Select Join other network from the Network Name menu, then select your network. Enter the password when prompted and save it in the keychain.

  • Itunes 9 Upgrade. Installs OK, but fails to run with 'Unknown Error(-50)'

    Been running Itunes versions 7/8 very happily. Upgraded to 9.0 today. After installing, which reported no problems, Itunes failed to run, reporting a missing reference in CoreFoundation.dll. I tried a re-install, but with no improvement. I the un-installed Itunes, re-imported the Itunes 9 setup file (88Mbytes), re-installed the product, and still it does not run, reporting a -50 Unknown Error.
    Not exactly impressive! I'd be grateful for any ideas, including how to revert to version 8. Thanks, ju

    Thanks for the pointer to the KB article. Error 1 is missing from the list provided by iTunes (more information), but I was afraid it means hardware. Will try on another computer, but I'm afraid the phone is sick.
    Thanks,
    Manfred

  • *** ERROR = Connect to database failed, rc = -4008 (POS(1) Unknown user na

    Hello
    I have just finished a dbcopy of Maxdb 7.6  to a new system with initilization.i can bring the db online. I have  ran the xuser command to fix the db users as below command as per note 39439
    i changed them in home dir of sidadm,sqdsid
                          xuser -U DEFAULT -u SAP<SID>,<password> -d <database_name> -n <database_server> -S SAPR3 -t 0 -I 0 set
    c) DBM user: for example, CONTROL.
                           xuser -U c -u CONTROL,<password> -d <database_name> -n <database_server> -S INTERNAL set
    d) SYSDBA user: for example, SUPERDBA.
                           xuser -U w -u SUPERDBA,<password> -d <database_name> -n <database_server> -S INTERNAL set 
    But iam having the below error now when trying to bring the SAP system up in dev_w0
    C  Try to connect (DEFAULT) onconnection 0 ...
    C
    C Mon Dec 19 21:46:11 2011
    C  *** ERROR => Connect to database failed, rc = -4008 (POS(1) Unknown user name/password combinati
    on)
    [dbsdbsql.cpp 137]
    B  ***LOG BY2=> sql error -4008  performing CON [dbsh#3 @ 1208] [dbsh    1208 ]
    B  ***LOG BY0=> POS(1) Unknown user name/password combination [dbsh#3 @ 1208] [dbsh    1208 ]
    B  ***LOG BY2=> sql error -4008  performing CON [dblink#8 @ 433] [dblink  0433 ]
    B  ***LOG BY0=> POS(1) Unknown user name/password combination [dblink#8 @ 433] [dblink  0433 ]
    M  ***LOG R19=> ThInit, db_connect ( DB-Connect 000256) [thxxhead.c   1537]
    M  in_ThErrHandle: 1
    M  *** ERROR => ThInit: db_connect (step 1, th_errno 13, action 3, level 1) [thxxhead.c   10837]
    M
    is there something  that i missed somewhere?
    Any ideas welcome

    erpsyscs1:cs1adm 46> xuser list
    XUSER Entry  1
    Key         :DEFAULT
    Username    :SAPCS1
    UsernameUCS2:S.A.P.C.S.1. . . . . . . . . . . . . . . . . . . . . . . . . . .
    Password    :?????????
    PasswordUCS2:?????????
    Dbname      :CS1
    Nodename    :erpsyscs1
    Sqlmode     :SAPR3
    Cachelimit  :-1
    Timeout    
    Isolation  
    Charset     :<unspecified>
    XUSER Entry  2
    Key         :c
    Username    :CONTROL
    UsernameUCS2:C.O.N.T.R.O.L. . . . . . . . . . . . . . . . . . . . . . . . . .
    Password    :?????????
    PasswordUCS2:?????????
    Dbname      :CS1
    Nodename    :erpsyscs1
    Sqlmode     :INTERNAL
    Cachelimit  :-1
    Timeout     :-1
    Isolation   :-1
    Charset     :<unspecified>
    XUSER Entry  3
    Key         :c_J2EE
    Username    :CONTROL
    UsernameUCS2:C.O.N.T.R.O.L. . . . . . . . . . . . . . . . . . . . . . . . . .
    Password    :?????????
    PasswordUCS2:?????????
    Dbname      :CS1
    Nodename    :erpsyscs1
    Sqlmode     :SAPR3
    Cachelimit  :-1
    Timeout    
    Isolation  
    Charset     :<unspecified>
    XUSER Entry  4
    Key         :w
    Username    :SUPERDBA
    UsernameUCS2:S.U.P.E.R.D.B.A. . . . . . . . . . . . . . . . . . . . . . . . .
    Password    :?????????
    PasswordUCS2:?????????
    Dbname      :CS1
    Nodename    :erpsyscs1
    Sqlmode     :INTERNAL
    Cachelimit  :-1
    Timeout     :-1
    Isolation   :-1
    Charset     :<unspecified>

  • MaxDB perl DBI and sql error -4008

    I'm using PERL DBI module to connect to my liveCache instances, as a read-only user, to obtain status of various things.
    I've installed the latest MaxDB DBI modules and latest MaxDB 7.7 Linux runtimes.
    I can successfully connect to a livecache 7.4 instance, but for some reason when I connect to a 7.6 instance I get a DBI error:
    sql error -4008
    failed: POS(1) Unknown user name/password combination
    My code is:
    $dbMAXDB = DBI->connect("dbi:MaxDB:$o_nodename/$o_SID",$maxdb_usr,$maxdb_pwd, \%dbi_attr) or die;
    The above code works with 7.5 etc, but not for my 1 single 7.6 instance!
    The username/pwd is correct, as using dbmcli with the same username/pwd works.
    Has anyone experienced this, or can someone offer a solution?

    Maybe you use the administrator user instead of the SQL user? MaxDB distinguishes between “Administrators” - as we called them - and “SQL users”. The group of “Administrators” (Database Manager operators, DBM operators) is used for the administration of the database only (start, stop, backup etc.) and cannot be used to open a SQL session. So please make sure that the user is a SQL user.
    Also you might check if you will be able to connect to the database with the command line tool sqlcli using this user.
    Regards,
    Marco

  • MaxDB to HANA replication via SLT suffers from 8 characters password limitation?

    Hi experts,
    We are trying to replicate data from a NW BPM instance (SAP NW PO (Java) on MaxDB with, let's say, sid PO7) via SLT to SAP HANA.
    (Version info: MaxDB 7.9, SLT DMIS 2011 SP5, HANA 1.0 SP6 Rev68.)
    So we use the ADBC connection route, via the DBCON table.
    We want to use the SAPPO7DB user because it is impossible (we think) to have another MaxDB-user connect to the SAPPO7DB (personal) SCHEMA with all the authorizations described in 1778969 - SAP LT Replication Server: Using MaxDB as non-SAP source .
    So we resort to the SAPPO7DB user who has a password of 8+ characters. Connecting via SQL Studio is no problem, however via DBCON and testing via ABAP report ADBC_CHECK_CONNECTION we get "sql error      4.008- occured:  POS(1) Unknown user name/password combination" errors.
    When connecting a DUMMY maxdb user with a passowrd of 8 chars, the connection test is successful. With a password of more than 8 chars, the test fails.
    So is the DBCON connectivity indeed suffering from the ancient 8 characters password limitation?
    If so, how to fix this? Our workaround would be to change the SAPPO7DB password to a new one of 8 characters in length. Of course, we want the PO system to keep on running, so in which configuration thingy would we need to change this password so the app server can connect to the db? (This is my lack of Java Basis knowledge showing...)
    Cheers, Wout

    Hi Wout,
    I am also performing similar replication from PO to HANA which is not working.
    Replication scenario : BPM(PO) -> SLT -> HANA
    Please see my post : Table BC_BPEM_EL_ENTRY not found in the control table DMC_MT_TABLES
    Please help if you have any idea on this? Thanks in advance.
    Cheers,
    Naresh

  • [SOLVED] update zfs fails due kernel version

    $ uname -v
    #1 SMP PREEMPT Sun Jun 8 10:08:38 CEST 2014
    and
    $ sudo pacman -Syu
    :: Synchronising package databases...
    core is up to date
    extra is up to date
    community is up to date
    demz-repo-core is up to date
    demz-repo-archiso is up to date
    :: Starting full system upgrade...
    resolving dependencies...
    looking for inter-conflicts...
    error: failed to prepare transaction (could not satisfy dependencies)
    :: spl-git: requires linux=3.14.6-1
    :: zfs-git: requires linux=3.14.6-1
    As I have the required kernel version, I'm puzzled why pacman couldn't do the update.
    Please enlighten me.
    Last edited by theking2 (2014-06-22 07:54:43)

    @Xi0N
    With spl{,-utils} and zfs{,-utils}, upgrading leads to circular dependencies.  This can be worked around by always building the packages in a chroot, but it is a bit more work than a normal module add on from the AUR.
    But while demizer's repo is super duper convenient, he is human and doesn't always get to updating the packages as soon as the new kernel drops to [core].  So from time to time, you will have to patiently wait for the unofficial repo to be updated before you can update the linux package.  That said, I am pretty sure he versions the dependency on the linux package, so I don't think that you can install the new linux package and then end up with a non-working filesystem.  Rather, the attempt to upgrade the linux package will fail due to unmet dependencies.
    Edit: As a disclaimer, it has been a while since I have played with zfs.  So while I think this information is accurate, things may or may not have changed.
    Last edited by WonderWoofy (2014-06-26 23:27:17)

  • APEX_LDAP.AUTHENTICATE fails with accented user names after upgrade 4.2.1

    Hello,
    We have a support contract so I already escalated this to Oracle support (awaiting reply now). But maybe someone else also has this problem.
    After the upgrade from APEX 4.1.1 to 4.2.1, one of our users couldn't log in any more into our application environment.
    We use authentication against MS Active Directory by calling the APEX_LDAP.AUTHENTICATE function.
    It took me some time to track down the problem. Apparently, the person with log in problems had a French character in his name ("é"), and this caused the APEX_LDAP.AUTHENTICATE to fail (it returns false, even when the user name/password are correct!). As a workaround, we replaced the "é" by "e" and now the user can log in again... This used to work fine with APEX 4.1.1!
    Any one with the same issue??
    Matthias
    http://matthiashoys.wordpress.com
    Edited by: mhoys on Apr 5, 2013 1:27 PM

    Thanks Howard! I don't think our problem is related to the APEX Listener (we are using the older version 1.1.4). When I call the APEX_LDAP.AUTHENTICATE function directly from a PL/SQL block (so by bypassing the web server), the problem remains...
    Matthias

  • R12.1.1 upgrade driver failed due to OKC user connectivity (RHEL 5.9)

    Hi Team,
    I was in the middle of the R12.1.1 upgrade and the driver failed due to OKC user connectivity .
    I have checked all the possibilities.
    Please let me know how to proceed from here. Though I restarted the patch it is failing due to OKC user login denied.
    Assigned: file as_accesses_n17.xdf on worker 1 for product as username APPS.
    Assigned: file cnpln.odf on worker 2 for product cn username CN.
    Assigned: file invtxhi.odf on worker 3 for product inv username INV.
    Assigned: file mscplan.odf on worker 4 for product msc username MSC.
    Assigned: file MSC_SYSTEM_ITEMS.xdf on worker 5 for product msc username APPS.
    Assigned: file OKCDAUT.odf on worker 6 for product okc username OKC.
    Assigned: file OKCDSUP.odf on worker 7 for product okc username OKC.
    Assigned: file OKCOTH1.odf on worker 8 for product okc username OKC.
    Assigned: file OKCPTY1.odf on worker 9 for product okc username OKC.
    Assigned: file OKCREP1.odf on worker 10 for product okc username OKC.
    Assigned: file OKCSHD1.odf on worker 11 for product okc username OKC.
    Assigned: file OKCVARL.odf on worker 12 for product okc username OKC.
    Assigned: file OKCXRPT.odf on worker 13 for product okc username OKC.
    Connecting to OKC......Unable to connect.
    AutoPatch error:
    The following ORACLE error:
    ORA-01017: invalid username/password; logon denied
    occurred while executing the SQL statement:
    CONNECT OKC/*****
    AutoPatch error:
    Error while evaluating "Check Object"
    Telling workers to quit...
    2 workers have quit. Waiting for 14 more.
    12 workers have quit. Waiting for 4 more.
    13 workers have quit. Waiting for 3 more.
    15 workers have quit. Waiting for 1 more.
    All workers have quit.
    AutoPatch error:
    Error running SQL and EXEC commands in parallel

    user11962637 wrote:
    Hi Srini,
    Thank you for the update.
    The password is working fine no issues with the connectivity from my end, but upgrade driver is failing with the same error.
    sqlplus apps/apps
    SQL*Plus: Release 10.1.0.5.0 - Production on Fri May 17 18:18:03 2013
    Copyright (c) 1982, 2005, Oracle. All rights reserved.
    Connected to:
    Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
    With the Partitioning, OLAP, Data Mining and Real Application Testing options
    SQL> conn okc/okc
    Connected.
    SQL> conn system/crp2system
    Connected.
    SQL> exitThis will happen if you change the password using the ALTER USER command rather than using the FNDCPASS executable
    Srini

Maybe you are looking for