Communcation link failure with HS ODBC to AS/400  (v4r3)

HI all,
i have problem when using Heterogeneous Service to connect Oralce to DB2/400 in AS/400 (v4r3).
I am using HS's ODBC to connect to DB2/400 in AS/400.
1) first I created a DSN with name AS400 and driver "Client Access ODBC Driver (32-bit)"
2) then configured HS in %ORACLE_HOME%/hs/admin/initodbc.ora
3) modified listener.ora as well as tnsnames.ora
4) restarted the listener and Oracle.
5) then I created the database link for this service.
create database link as400
connect to "USER" identified by "PASSWRD"
using 'as400';but when I tried to select something from DB2/400. i encountered the following error
select count(*) from grw99.sitsupp@as400ORA-28500: connection from ORACLE to a non-Oracle system returned this message:
[Generic Connectivity Using ODBC][IBM][Client Access ODBC Driver (32-bit)]
[DB2/400 SQL]Communication link failure. COMM RC=0x5 (SQL State: 08S01; SQL Code: -5)
ORA-02063: preceding 2 lines from HSODBC
can anyone tell me why?!!
pls help me!
Marco

Sounds like the IBM SQLExtendedFetch bug within the IBM ODBC driver.
Please add these parameters to your DG4ODBC configuration file initDB2_SID.ora:
HS_FDS_FETCH_ROWS=1
HS_RPC_FETCH_REBLOCKING=off
Then open a new SQL*Plus session and retry the select.

Similar Messages

  • Performance Release causes link failure with undefined ref to `__sincos'

    I noticed while building a shared library with performance release for the C compiler that linking to the library has problems due to an undefined reference to __sincos. This is a mixed fortran and c library. The fortran is fine being compiled with performance release. Everything works with the library compiled with Release for the C portion and Performance Release for the Fortran portion.
    Is there anything I can do to find out if this is my problem or a problem with the compiler?

    I discussed this problem with an engineer from the C
    compiler team. He pointed out that the likely cause of
    the problem is that the option -xlibmopt is being
    specified on the command line for compilation, but not
    on the command line for linking. If the option -xlibmopt
    is used for any of the compilations, it must also be used
    for linking.
    The option -xlibmopt causes the library libmopt to be added
    to the link line. The library libmopt includes the entry point
    __sincos. The reason the program links successfully on
    Solaris is that the Solaris libraries include another version
    of the routine __sincos in another library. That version of
    __sincos is not as efficient as the version in libmopt.
    Bob Corbett

  • Linker Error during compiling ODBC WinCE C++_Sample Project

    I am devloping a ODBC application for PocketPC2003 using OLite 10g Release 10.3.0.2. before that i am understanding the sample application provided with Olite.
    I followed all the instructions provided in ReadMe.txt file available before using VC++ sample. After making all the settings and compiling i am getting following linker errors as mentioned below.
    Any solution for this problem at the earliest will be appreciated, i have tried link all the libraries provided with WinCE armv4.
    Linker Error Messages:
    Error     1     error LNK2019: unresolved external symbol SQLExecDirect referenced in function "public: virtual __cdecl CSQLResult::~CSQLResult(void)" (??1CSQLResult@@UAA@XZ)     dbaccess.obj     
    Error     2     error LNK2019: unresolved external symbol SQLFreeStmt referenced in function "public: virtual __cdecl CSQLResult::~CSQLResult(void)" (??1CSQLResult@@UAA@XZ)     dbaccess.obj     
    Error     3     error LNK2019: unresolved external symbol SQLGetData referenced in function "public: class CRowObj const * __cdecl CSQLResult::Fetch(int)" (?Fetch@CSQLResult@@QAAPBVCRowObj@@H@Z)     dbaccess.obj     
    Error     4     error LNK2019: unresolved external symbol SQLFetch referenced in function "public: class CRowObj const * __cdecl CSQLResult::Fetch(int)" (?Fetch@CSQLResult@@QAAPBVCRowObj@@H@Z)     dbaccess.obj     
    Error     5     error LNK2019: unresolved external symbol SQLFreeEnv referenced in function "public: void __cdecl COLiteDB::Disconnect(void)" (?Disconnect@COLiteDB@@QAAXXZ)     dbaccess.obj     
    Error     6     error LNK2019: unresolved external symbol SQLFreeConnect referenced in function "public: void __cdecl COLiteDB::Disconnect(void)" (?Disconnect@COLiteDB@@QAAXXZ)     dbaccess.obj     
    Error     7     error LNK2019: unresolved external symbol SQLDisconnect referenced in function "public: void __cdecl COLiteDB::Disconnect(void)" (?Disconnect@COLiteDB@@QAAXXZ)     dbaccess.obj     
    Error     8     error LNK2019: unresolved external symbol SQLConnect referenced in function "public: int __cdecl COLiteDB::Connect(void)" (?Connect@COLiteDB@@QAAHXZ)     dbaccess.obj     
    Error     9     error LNK2019: unresolved external symbol SQLAllocConnect referenced in function "public: int __cdecl COLiteDB::Connect(void)" (?Connect@COLiteDB@@QAAHXZ)     dbaccess.obj     
    Error     10     error LNK2019: unresolved external symbol SQLAllocEnv referenced in function "public: int __cdecl COLiteDB::Connect(void)" (?Connect@COLiteDB@@QAAHXZ)     dbaccess.obj     
    Error     11     error LNK2019: unresolved external symbol SQLError referenced in function "public: class CSQLResult * __cdecl COLiteDB::Execute(wchar_t const *)" (?Execute@COLiteDB@@QAAPAVCSQLResult@@PB_W@Z)     dbaccess.obj     
    Error     12     error LNK2019: unresolved external symbol SQLDescribeCol referenced in function "public: class CSQLResult * __cdecl COLiteDB::Execute(wchar_t const *)" (?Execute@COLiteDB@@QAAPAVCSQLResult@@PB_W@Z)     dbaccess.obj     
    Error     13     error LNK2019: unresolved external symbol SQLNumResultCols referenced in function "public: class CSQLResult * __cdecl COLiteDB::Execute(wchar_t const *)" (?Execute@COLiteDB@@QAAPAVCSQLResult@@PB_W@Z)     dbaccess.obj     
    Error     14     error LNK2019: unresolved external symbol SQLAllocStmt referenced in function "public: class CSQLResult * __cdecl COLiteDB::Execute(wchar_t const *)" (?Execute@COLiteDB@@QAAPAVCSQLResult@@PB_W@Z)     dbaccess.obj

    Hi,
    The OLITE forum (Database Mobile Server (inc. legacy Database Lite) would be a better place to post your issue. This forum deals with the ODBC driver that connects to a "normal" Oracle database.
    Hope it helps,
    Greg
    Edited by: gdarling on Nov 12, 2008 8:31 AM

  • ColdFusion 10 - MySQL Communications link failure

    We are migrating some websites onto a cloud infrastructure running Windows 2008 virtual machines.  These websites all run on ColdFusion with MySQL databases.  They currently are running in our CoLo with no problems.  Additionally, they are running on our development network in our offices with no problems.
    We are setting up our cloud to match as closely as possible the configuration we currently use which is, essentially, CF10 + IIS on one server and MySQL on a separate machine.  We are 99% finished and most things are running great.  However....
    We have run into a couple, as in 2, places where we click a link/button and are greeted with:
    Error Executing Database Query.
    Communications link failure The last packet successfully received from the server was 0 milliseconds ago. The last packet sent successfully to the server was 0 milliseconds ago.
    Scanning the stack-trace I also find:
    `Caused by: java.net.SocketException: Connection reset`
    The communications link error is ALWAYS: 0ms.
    What's most puzzling is the Queries that seem to be causing this are *simple* queries that are used ALL OVER the sites with no problems.  Why they are failing at hese 2 particular places has us at wits end.
    Our only clue is, looking at the CF Error description of what scripts are called, we can see the script where the query is failing is getting called twice?  For example, one of the occurences is in our Application file:
        >The error occurred in D:/Our_Web_Sites/oursite/Application.cfm: line 73
        >Called from D:/Our_Web_Sites/oursite/Application.cfm: line 17
        >Called from D:/Our_Web_Sites/oursite/Application.cfm: line 1
        >Called from D:/Our_Web_Sites/oursite/Application.cfm: line 73
        >Called from D:/Our_Web_Sites/oursite/Application.cfm: line 17
        >Called from D:/Our_Web_Sites/oursite/Application.cfm: line 1
    We can find nothing in our CF code that would be causing the script to be called twice so our guess is the first call is failing on the Query so CF tries again...only to fail and error.
    Googling this issue I've found lots of posts about changing the MySQL timeouts.  None of those worked and I didn't expect them to since what we're dealing with doesn't appear to be a timeout issue.  These pages fail each and every time.
    The closest we've come to a solution came from this blog posting:
    http://www.talkingtree.com/blog/index.cfm/2011/1/12/Validation-Query-for-MySQL-communicati ons-link-failure
    If we UNCHECK the "Maintain connections across client requests. " setting in CFAdmin then the error goes away.  The blog suggests leaving that checked, which is our preference, and using Connection Validation of "SELECT 1;".  Try that...same error.
    We've also tried the JDBC AutoConnect=true option.  No effect.
    Downloaded latest JDBC Connector and used it instead of standard CF10-MySQL connector.  No effect.
    Again, 99% of the site works with the exception of these two links, both of which work just fine in all our other environments.  Any other ideas?

    I have some questions.
    1) You talk of 2 calls. However, you show us 5 calls from Application.cfm. What do those line numbers tell us?
    2) Shouldn't that be AutoReconnect=true rather than AutoConnect=true? In any case, it seems that the problem here is that ColdFusion attempts to use a stale connection to the database. It is then usually preferable to change wait_timeout instead. The MySQL documentation says, 'Alternatively[to AutoReconnect=true], as a last option, investigate setting the MySQL server variable "wait_timeout" to a high value, rather than the default of 8 hours.'.
    3) Shouldn't you already convert to Application.cfc?

  • Problem with jdbc:odbc returning incorrect number of rows.

    Hello,
    Am sure i have done something stupid, but i have an issue with jdbc:odbc ....
    It is a simple sceanrio that i have coded umpteen times before ...
    I have the following ....
    1. Connection to DB2 on an IBM i5 (I apologise for not using native drivers from jt400.jar, but i had an ODBC code example and was in a rush - no excuse i know)
    2. Statement object created from connection above
    3. A string with my SQL in it
    4. A result set for the results.
    These are created as follows:
    Class.forName( "sun.jdbc.odbc.JdbcOdbcDriver");
    con = DriverManager.getConnection(ODBCSource, userID, password);
    if (con == null) {
    // error handling not relevant here
    } else {
    Statement s = con.createStatement(ResultSet.TYPE_SCROLL_INSENSITIVE, ResultSet.CONCUR_UPDATABLE);
    String SQL = "select * from table";
    ResultSet rs = s.executeQuery(SQL);
    i then try to loop ....
    while (rs.next() )
    // stuff
    however, i only ever get one result .... if i stick in the check for isLast, the first loop hits this check, i get my little status message, and the loop ends.
    while (rs.next() )
    if (rs.isLast() )
    System.out.println("I am on last record");
    BUT if i run the SQL
    "select count(*) from table" ... i get a count of 148 !!
    I tried setting the FetchSize through setFetchSize(), but made no difference.
    This is running on a JBoss server 4.2.1GA, JDK is "jdk1.6.0_02" .... i have a suspicion that this may be a JBoss specfic issue, as this exact code runs just fine on the Domino platform that it was originally on, if this is the case, i apologise for wasting everyones time .... but would still appreciate any pointers you can give me.
    Cheers

    Hello,
    Thanks for the reply, I am not sure i follow what you are saying.
    I only mentioned JBoss as it is the application server that we have deployed to and because the orignal code ran fine on a Domino server, I will take your advice and try to run it through in debug rather than running actually on the application server.
    Am i incorrect in my assumption that if "select count(*) from table" gives a count of 148, i should expect 148 records in a result set created from "select * from table" ? This is all rather new to me so i apologise if this is incorrect, I'd love to know why this is incorrect so i dont make similar mistakes in future.
    Also, If i run this same code on the previous platform, i get 148 iterations of the code contained within
    while (rs.next() ) { ... }
    When the war file is deployed to JBoss, the same SQL statement gives a result set that only iterates once for
    while (rs.next() ) { ... }
    The previous platform as I say was domino, but it was running as a lotus notes java agent (despite not using any notes documents etc) as it happened to be where the web pages that call this process were located. It is possible that some of the main code has changed as I had cut and paste the code into a servlet using MyEclipse, but i have double checked the bit that does this SQL request and it is identical
    To complete the picture, the new servelt is then called from the action tag on the submit form on a JSP, when it ends the servlet redirects via the requestdispacher to success or failure jsp pages depending on the outcome of the processing.
    Thank you again for your help.

  • Cisco 6880-x vsl link failure

    Hi Guys,
    I have a head scratcher that I'm dealing with.  I have 2x (2 month) 6880-x switches configured with vss with 2 vsl links on each of its sup cards and switch 1 is the active switch on the vss.  Both 6880x chassis also have 2 additional 10g modules each.  I am dealing with 2 issues in this setup.  
    The first issue is,  i have a 3750x with a 10g module thats port channeled to the vss with one 10g link going to each of the chassis.  Within the first 3 days it started dropping the link that's plugged to switch1, then comes back on right away.  It does it randomly throughout the day.  I have changed out the optics on both ends, changed the cable, and also changed the module on the 3750x and I still get the same issue.  The strange part is that when switch2 on the vss becomes the active switch, the problem goes away.  I did notice this before changing out the optics, cable, module on the 3750x.
    The second issue is the one I'm been trying to figure out along with cisco TAC.  This started about a month after bring the vss online.  When switch1 was the active switch in the vss, every couple of days vsl links drop one at a time, eventually killing the vss and putting the standby unit into recovery mode because of the dual active detection.  once I reboot the standby switch, the vss comes back up normally.  it did this a couple of times until I decided to force switch2 to be the active switch on the vss.  when switch2 became active, the vss was stable for about a month then the vsl links died again, and the system failed over to switch1.  after looking at the logs with cisco tac, we see that the vsl links stop responding which causes the failover, but up until now we still can't determine what is causing the vsl links to fail.  cisco tac said that maybe the vsl links were being overloaded but we have been monitoring the bandwidth utilization on the vsl links and they never go beyond 1% utilization.  The last suggestion by cisco tac was to add another vsl link but through another module other than the sup.  This was done a couple of days ago so now i'm waiting to see if the vsl links fail again and since switch1 is the active switch on the vss, i'm having to deal with the first issue above with the 3750x.
    I've included some log entries from the dropped port-channel member and also logs for when the vsl links fail.
    Logs for 3750x port-channel member drops.
    *Jul  5 05:27:10 PDT: %LINEPROTO-SW1-5-UPDOWN: Line protocol on Interface TenGigabitEthernet2/2/5, changed state to down
    *Jul  5 05:27:10 PDT: %LINK-SW1-3-UPDOWN: Interface TenGigabitEthernet2/2/5, changed state to down
    *Jul  5 05:27:10 PDT: %LINK-SW1-3-UPDOWN: Interface TenGigabitEthernet2/2/5, changed state to up
    *Jul  5 05:28:10 PDT: %LINEPROTO-SW1-5-UPDOWN: Line protocol on Interface TenGigabitEthernet2/2/5, changed state to up
    *Jul  6 11:28:52 PDT: %LINEPROTO-SW1-5-UPDOWN: Line protocol on Interface TenGigabitEthernet2/2/5, changed state to down
    *Jul  6 11:28:52 PDT: %LINK-SW1-3-UPDOWN: Interface TenGigabitEthernet2/2/5, changed state to down
    *Jul  6 11:28:53 PDT: %LINK-SW1-3-UPDOWN: Interface TenGigabitEthernet2/2/5, changed state to up
    *Jul  6 11:29:53 PDT: %LINEPROTO-SW1-5-UPDOWN: Line protocol on Interface TenGigabitEthernet2/2/5, changed state to up
    *Jul  7 06:27:25 PDT: %LINEPROTO-SW1-5-UPDOWN: Line protocol on Interface TenGigabitEthernet2/2/5, changed state to down
    *Jul  7 06:27:25 PDT: %LINK-SW1-3-UPDOWN: Interface TenGigabitEthernet2/2/5, changed state to down
    *Jul  7 06:27:26 PDT: %LINK-SW1-3-UPDOWN: Interface TenGigabitEthernet2/2/5, changed state to up
    *Jul  7 06:27:33 PDT: %LINEPROTO-SW1-5-UPDOWN: Line protocol on Interface TenGigabitEthernet2/2/5, changed state to up
    *Jul  7 06:33:43 PDT: %LINEPROTO-SW1-5-UPDOWN: Line protocol on Interface TenGigabitEthernet2/2/5, changed state to down
    *Jul  7 06:33:43 PDT: %LINK-SW1-3-UPDOWN: Interface TenGigabitEthernet2/2/5, changed state to down
    *Jul  7 06:33:43 PDT: %LINK-SW1-3-UPDOWN: Interface TenGigabitEthernet2/2/5, changed state to up
    *Jul  7 06:34:43 PDT: %LINEPROTO-SW1-5-UPDOWN: Line protocol on Interface TenGigabitEthernet2/2/5, changed state to up
    *Jul  7 07:38:35 PDT: %LINEPROTO-SW1-5-UPDOWN: Line protocol on Interface TenGigabitEthernet2/2/5, changed state to down
    *Jul  7 07:38:35 PDT: %LINK-SW1-3-UPDOWN: Interface TenGigabitEthernet2/2/5, changed state to down
    *Jul  7 07:38:36 PDT: %LINK-SW1-3-UPDOWN: Interface TenGigabitEthernet2/2/5, changed state to up
    log for VSL link failures
    *Jun 27 23:59:25 PDT: %VSLP-SW2-3-VSLP_LMP_FAIL_REASON: Te2/5/15: Link down
    *Jun 27 23:59:25 PDT: %VSL-SW2-5-VSL_CNTRL_LINK:  New VSL Control Link  2/5/16 
    *Jun 27 23:59:25 PDT: %LINEPROTO-SW2-5-UPDOWN: Line protocol on Interface TenGigabitEthernet2/5/15, changed state to down
    *Jun 27 23:59:25 PDT: %LINEPROTO-SW2-5-UPDOWN: Line protocol on Interface TenGigabitEthernet1/5/15, changed state to down
    *Jun 27 23:59:25 PDT: %LINK-SW2-3-UPDOWN: Interface TenGigabitEthernet2/5/15, changed state to down
    *Jun 27 23:59:25 PDT: %VSLP-SW2-3-VSLP_LMP_FAIL_REASON: Te2/5/16: Link down
    *Jun 27 23:59:25 PDT: %VSLP-SW2-2-VSL_DOWN:   Last VSL interface Te2/5/16 went down
    *Jun 27 23:59:25 PDT: %VSLP-SW2-2-VSL_DOWN:   All VSL links went down while switch is in ACTIVE role
    *Jun 27 23:59:25 PDT: %LINEPROTO-SW2-5-UPDOWN: Line protocol on Interface TenGigabitEthernet2/5/16, changed state to down
    *Jun 27 23:59:25 PDT: %LINEPROTO-SW2-5-UPDOWN: Line protocol on Interface Port-channel2, changed state to down
    *Jun 27 23:59:25 PDT: %LINK-SW2-3-UPDOWN: Interface Port-channel2, changed state to down
    *Jun 27 23:59:25 PDT: %LINK-SW2-3-UPDOWN: Interface TenGigabitEthernet2/5/16, changed state to down
    *Jun 27 23:59:25 PDT: %LINEPROTO-SW2-5-UPDOWN: Line protocol on Interface Port-channel1, changed state to down
    *Jun 27 23:59:25 PDT: %LINK-SW2-3-UPDOWN: Interface Port-channel1, changed state to down
    *Jun 27 23:59:25 PDT: %OIR-SW2-6-INSREM: Switch 1 Physical Slot 5 - Module Type LINE_CARD  removed 
    *Jun 27 23:59:25 PDT: %OSPF-SW2-5-ADJCHG: Process 1, Nbr 10.253.0.3 on TenGigabitEthernet1/1/1 from FULL to DOWN, Neighbor Down: Interface down or detached
    *Jun 27 23:59:25 PDT: %LINEPROTO-SW2-5-UPDOWN: Line protocol on Interface Port-channel24, changed state to down
    *Jun 27 23:59:25 PDT: %LINK-SW2-3-UPDOWN: Interface Port-channel24, changed state to down
    *Jun 27 23:59:26 PDT: %OIR-SW2-6-INSREM: Switch 1 Physical Slot 1 - Module Type LINE_CARD  removed 
    *Jun 27 23:59:26 PDT: %LINK-SW2-3-UPDOWN: Interface Port-channel17, changed state to down
    *Jun 27 23:59:26 PDT: %PFREDUN-SW2-6-ACTIVE: Standby processor removed or reloaded, changing to Simplex mode
    *Jun 27 23:59:26 PDT: %OIR-SW2-6-INSREM: Switch 1 Physical Slot 2 - Module Type LINE_CARD  removed 
    *Jun 27 23:59:27 PDT: %LINK-SW2-3-UPDOWN: Interface TenGigabitEthernet1/5/14, changed state to down
    *Jun 27 23:59:27 PDT: %LINK-SW2-3-UPDOWN: Interface TenGigabitEthernet1/5/15, changed state to down
    *Jun 27 23:59:27 PDT: %LINK-SW2-3-UPDOWN: Interface TenGigabitEthernet1/5/16, changed state to down
    *Jun 27 23:59:27 PDT: %LINEPROTO-SW2-5-UPDOWN: Line protocol on Interface TenGigabitEthernet1/5/14, changed state to down
    *Jun 27 23:59:27 PDT: %LINEPROTO-SW2-5-UPDOWN: Line protocol on Interface TenGigabitEthernet1/5/16, changed state to down
    *Jun 27 23:59:27 PDT: %LINK-SW2-3-UPDOWN: Interface TenGigabitEthernet1/1/1, changed state to down
    *Jun 27 23:59:27 PDT: %LINK-SW2-3-UPDOWN: Interface TenGigabitEthernet1/1/2, changed state to down
    *Jun 27 23:59:27 PDT: %LINK-SW2-3-UPDOWN: Interface TenGigabitEthernet1/1/3, changed state to down
    *Jun 27 23:59:27 PDT: %LINEPROTO-SW2-5-UPDOWN: Line protocol on Interface TenGigabitEthernet1/1/1, changed state to down
    *Jun 27 23:59:27 PDT: %LINEPROTO-SW2-5-UPDOWN: Line protocol on Interface TenGigabitEthernet1/1/2, changed state to down
    *Jun 27 23:59:27 PDT: %LINEPROTO-SW2-5-UPDOWN: Line protocol on Interface TenGigabitEthernet1/1/3, changed state to down
    Press RETURN to get started!
    *Jun 28 07:03:33.421: %USBFLASH-SW2_STBY-5-CHANGE: bootdisk has been inserted!
    *Jun 28 07:03:53.297: %OIR-SW2_STBY-6-INSPS: Power supply inserted in slot 1
    *Jun 28 07:03:53.301: %C6KPWR-SW2_STBY-4-PSOK: power supply 1 turned on.
    *Jun 28 07:04:26.093: %FABRIC-SW2_STBY-5-FABRIC_MODULE_ACTIVE: The Switch Fabric Module in slot 5 became active.
    *Jun 28 07:04:48.497: %DIAG-SW2_STBY-6-RUN_MINIMUM: Switch 2 Module 5: Running Minimal Diagnostics...
    *Jun 28 07:04:48.497: %CONST_DIAG-SW2_STBY-6-DIAG_PORT_SKIPPED: Module 5 port 15 is skipped in TestLoopback due to: the port is used as a VSL link.
    *Jun 28 07:04:48.497: %CONST_DIAG-SW2_STBY-6-DIAG_PORT_SKIPPED: Module 5 port 16 is skipped in TestLoopback due to: the port is used as a VSL link.
    *Jun 28 07:04:55.049: %CONST_DIAG-SW2_STBY-6-DIAG_PORT_SKIPPED: Module 5 port 15 is skipped in TestFexModeLoopback due to: the port is used as a VSL link.
    *Jun 28 07:04:55.049: %CONST_DIAG-SW2_STBY-6-DIAG_PORT_SKIPPED: Module 5 port 16 is skipped in TestFexModeLoopback due to: the port is used as a VSL link.
    *Jun 28 07:05:00.165: %CONST_DIAG-SW2_STBY-6-DIAG_PORT_SKIPPED: Module 5 port 15 is skipped in TestL2CTSLoopback due to: the port is used as a VSL link.
    *Jun 28 07:05:00.165: %CONST_DIAG-SW2_STBY-6-DIAG_PORT_SKIPPED: Module 5 port 16 is skipped in TestL2CTSLoopback due to: the port is used as a VSL link.
    *Jun 28 07:05:06.049: %CONST_DIAG-SW2_STBY-6-DIAG_PORT_SKIPPED: Module 5 port 15 is skipped in TestL3CTSLoopback due to: the port is used as a VSL link.
    *Jun 28 07:05:06.049: %CONST_DIAG-SW2_STBY-6-DIAG_PORT_SKIPPED: Module 5 port 16 is skipped in TestL3CTSLoopback due to: the port is used as a VSL link.
    *Jun 28 07:05:23.309: %DIAG-SW2_STBY-6-DIAG_OK: Switch 2 Module 5: Passed Online Diagnostics
    *Jun 28 00:05:38 PDT: %SYS-SW2_STBY-6-CLOCKUPDATE: System clock has been updated from 00:05:38 PDT Sat Jun 28 2014 to 00:05:38 PDT Sat Jun 28 2014, configured from console by console.
    *Jun 28 00:05:38 PDT: %SYS-SW2_STBY-6-CLOCKUPDATE: System clock has been updated from 00:05:38 PDT Sat Jun 28 2014 to 00:05:38 PDT Sat Jun 28 2014, configured from console by console.
    *Jun 28 00:05:38 PDT: %SSH-SW2_STBY-5-DISABLED: SSH 2.0 has been disabled
    *Jun 28 00:05:54 PDT: %SYS-SW2_STBY-5-RESTART: System restarted --
    Cisco IOS Software, c6880x Software (c6880x-ADVENTERPRISEK9-M), Version 15.1(2)SY2, RELEASE SOFTWARE (fc3)
    Technical Support: http://www.cisco.com/techsupport
    Copyright (c) 1986-2014 by Cisco Systems, Inc.
    Compiled Wed 26-Feb-14 15:30 by prod_rel_team
    *Jun 28 00:05:54 PDT: %SSH-SW2_STBY-5-ENABLED: SSH 2.0 has been enabled
    *Jun 28 00:05:54 PDT: %SYS-SW2_STBY-3-LOGGER_FLUSHED: System was paused for 00:03:01 to ensure console debugging output.
    *Jun 28 00:05:56 PDT: %C6KENV-SW2_STBY-4-LOWER_SLOT_EMPTY: The lower adjacent slot of module 5 might be empty. Airdam must be installed in that slot to be NEBS compliant
    *Jun 28 00:07:36 PDT: %DIAG-SW2_STBY-6-RUN_MINIMUM: Switch 2 Module 1: Running Minimal Diagnostics...
    *Jun 28 00:07:37 PDT: %SYS-SW2_STBY-3-LOGGER_FLUSHED: System was paused for 00:01:29 to ensure console debugging output.
    *Jun 28 00:07:41 PDT: %DIAG-SW2_STBY-6-RUN_MINIMUM: Switch 2 Module 2: Running Minimal Diagnostics...
    *Jun 28 00:08:10 PDT: %DIAG-SW2_STBY-6-DIAG_OK: Switch 2 Module 1: Passed Online Diagnostics
    *Jun 28 00:08:22 PDT: %EC-SW2_STBY-5-CANNOT_BUNDLE2: Te2/1/10 is not compatible with Te1/2/10 and will be suspended (Operational flow control send of Te2/1/10 is off, Te1/2/10 is on)
    *Jun 28 00:08:31 PDT: %EC-SW2_STBY-5-COMPATIBLE: Te2/1/10 is compatible with port-channel members
    *Jun 28 00:08:45 PDT: %DIAG-SW2_STBY-6-DIAG_OK: Switch 2 Module 2: Passed Online Diagnostics
    *Jun 28 00:08:46 PDT: %C6KENV-SW2_STBY-4-HIGHER_SLOT_EMPTY: The higher adjacent slot of module 2 might be empty. Airdam must be installed in that slot to be NEBS compliant
    ELDC1C1-AG01-1 line 0 
    ************************ W A R N I N G ***************************
    * THIS IS A PRIVATE COMPUTER SYSTEM, AND FOR AUTHORIZED USE ONLY.*
    * THIS SYSTEM IS MONITORED, AND ANY UNAUTHORIZED USE MAY BE      *
    * SUBJECT TO CRIMINAL PROSECUTION.                               *
    * IF YOU ARE NOT AUTHORIZED, LOG OUT IMMEDIATELY!!!!!            *
    so according to the logs, it seems like the switch was reloaded or something of the nature but even the cisco tac said that it wasnt the case but couldnt determine whats causing it either.  Tac went through the config on the vss and has said that its configured correctly.
    Maybe someone else has experienced this issue or if someone can point out something that I can look at...  sorry for the very long post.
    thanks

    I suppose, we have the same problem. Only when Switch 1 is the active switch of the 6880-X VSS system, the connection to the FEX-stack breaks suddenly after running fine for some days and the FEX-stack (3 x 6800-IA) get only ready again when I reset the whole VSS-system, both VSS-switches and the FEX-stack.
    All access ports at the FEX can't connect to our infrastructure (DHCP,DNS...). The two connected TenG FEX-stack uplinks sometimes get down and sometimes only the uplink to the active parent switch get down. The SYST LED of FEX 1 lighting amber.
    When parent switch 2 is the active unit the issue never occured.
    6880-X running with 15.2(1)SY, 6800-IA running with 15.2(3)E.
    Cisco TAC is investigating that issue, but till now without any result.
    When the issue occurs, the recorded logging messages are:
    Syslog 6880-X
    Apr  7 07:42:43.182: %PLATFORM_RPC-3-MSG_THROTTLED: RPC Msg Dropped by throttle mechanism: type 3, class 21, max_msg 32, total throttled 1274 (FEX-101)
    Apr  7 07:45:43.181: %PLATFORM_RPC-3-MSG_THROTTLED: RPC Msg Dropped by throttle mechanism: type 3, class 21, max_msg 32, total throttled 1276 (FEX-101)
    Syslog 6800-IA:
    Apr  7 07:57:43.182: %PLATFORM_RPC-3-MSG_THROTTLED: RPC Msg Dropped by throttle mechanism: type 3, class 21, max_msg 32, total throttled 1284
    -Traceback= 5198C4z 21413F8z 1C3B35Cz 1C3C6FCz 1C3CA00z 2654CC0z 26509BCz
    Apr  7 08:00:43.181: %PLATFORM_RPC-3-MSG_THROTTLED: RPC Msg Dropped by throttle mechanism: type 3, class 21, max_msg 32, total throttled 1286
    -Traceback= 5198C4z 21413F8z 1C3B35Cz 1C3C6FCz 1C3CA00z 2654CC0z 26509BCz

  • Can I create a linked server to this ODBC datasource (odbc driver by Progress OpenEdge) on Sql Server 2000 ?

    I installed the Progress OpenEdge ODBC driver for 32 bit database on my win7 workstation -- I used odbcad32.exe located at C:\Windows\SysWOW64 to configure the driver for 32 bit applications -- per the screen Shots here and I am able to connect to the datasource
    from Excel Query.
    I am able to connect to this ODBC datasource from Excel Query and see all the tables -- as in the screen shot.  I can also access this datasource from a C# app.
    Question:  if I can connect to this ODBC datasource from Excel -- does this mean I should be able to create a linked server to it?  I tried the following from SSMS Linked Serber Wizard on a Sql Server 2000 (I have used the Linked server wizard
    successfully in the past as well as linking with Tsql SPs).  This will at least create a mock Linked server on the Sql server 2000 (this does not work on sql server 2008 -- I tried), but when I try to view the catalogs -- I get the error in the screen
    shot below.  If the answer to my question is "YES" yes I should be able to create a linked server to this ODBC datasource what is the way to do this?  I added the UserID and Password in the Security tab, but I did not see where to add the
    port (4000).  What do I enter for the Product Name?  Can it be arbitrary or does it have to be something specific?
    Rich P

    Yes, you should be able to set up this as a linked server - from a 32-bit instance of SQL Server. That is, you can't use a 32-bit driver on 64-bit SQL Server. Now, since you have SQL 2000, I assume that this is a 32-bit instance. (But there was a 64-bit
    version for Itanium of SQL 2000.)
    For the Provider string, I would guess that you should enter something like
    Driver={Progress 11.3 OpenEdge Driver}
    just like you do in your application code.
    Basically, in the provider string, you specify your connection string, except that you take out the provider name, which is a separate parameter to sp_addlinkedserver. Since I know nothing about Progress, I can't give any specific details.
    The error message you get is somewhat puzzling, since this refers to SQLOLEDB which is the provider to access an SQL Server instance.
    Erland Sommarskog, SQL Server MVP, [email protected]

  • SEVERE: com.mysql.jdbc.exceptions.jdbc4 : Communicat link failure

    Hi,
    I am developing web application using jsf2.0. problem is ,
    when we interact with servlet by single person, It working fine. but when we interact with servlet by more then one person at same time. server throws error
    SEVERE: com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: Communications link failure
    Last packet sent to the server was 0 ms ago.
    How to solve the problem.
    server :Glashfish v3
    db :mysql 5.0
    thanks in advance.

    You must use a connection and then immediately close it.

  • Link Problem with libgc_dbg

    Hi there,
    I'm using Forte6 on Sun SPARC Solaris 2.7. When trying to use the memory monitor tool from the Forte6 environment I get a link failure:
    <code>
    $ CC -v -library=gc_dbg -o memtest memtest.C
    ### CC: Note: LM_LICENSE_FILE = 1726@licserva:1726@licservb:1726@licservc
    ### CC: Note: NLSPATH = /opt/forte_6.0/bin/../WS6/bin/../lib/locale/%L/LC_MESSAGES/%N.cat:/opt/forte_6.0/bin/../WS6/bin/../../lib/locale/%L/LC_MESSAGES/%N.cat
    /opt/forte_6.0/bin/../WS6/bin/ccfe -y-o -ymemtest.o -y-fbe -y/opt/forte_6.0/bin/../WS6/bin/fbe -y-xarch=generic -y-verbose -O0 -ptf /tmp/24540%1.%2 -ptx /opt/forte_6.0/bin/../WS6/bin/CC -ptk "-v -library=gc_dbg -xs " -D__SunOS_5_7 -D__SUNPRO_CC=0x510 -Dunix -Dsun -Dsparc -D__sparc -D__unix -D__sun -D__BUILTIN_VA_ARG_INCR -D__SVR4 -D__SUNPRO_CC_COMPAT=5 -y-s -instlib=/opt/forte_6.0/WS6/lib/libCstd.a -I/opt/forte_6.0/WS6/include/CC/Cstd -I/opt/forte_6.0/WS6/include/CC -I/opt/forte_6.0/WS6/include/CC/rw7 -I/opt/forte_6.0/WS6/include/cc -D__SUN_PREFETCH memtest.C -s /tmp/ccfe.24540.0.s
    /opt/forte_6.0/bin/../WS6/bin/CClink -ptk "-v -library=gc_dbg -xs -xildoff " -ptx /opt/forte_6.0/bin/../WS6/bin/CC memtest.o -o memtest
    ### CC: Note: LM_LICENSE_FILE = 1726@licserva:1726@licservb:1726@licservc
    ### CC: Note: NLSPATH = /opt/forte_6.0/bin/../WS6/bin/../lib/locale/%L/LC_MESSAGES/%N.cat:/opt/forte_6.0/bin/../WS6/bin/../../lib/locale/%L/LC_MESSAGES/%N.cat:/opt/forte_6.0/bin/../WS6/bin/../lib/locale/%L/LC_MESSAGES/%N.cat:/opt/forte_6.0/bin/../WS6/bin/../../lib/locale/%L/LC_MESSAGES/%N.cat
    ### CC: Note: LD_LIBRARY_PATH = /opt/www/lib/rvplayer:/opt/forte_6.0/WS6/lib:/opt/X11R6/lib:/usr/lib:/usr/local/lib
    ### CC: Note: LD_RUN_PATH = (null)
    ### CC: Note: LD_OPTIONS = (null)
    /usr/ccs/bin/ld -u __1cH__CimplKcplus_init6F_v_ -R/opt/forte_6.0/lib/rw7:/opt/forte_6.0/lib:/usr/ccs/lib:/usr/lib:/opt/SUNWspro/lib -o memtest /opt/forte_6.0/WS6/lib/crti.o /opt/forte_6.0/WS6/lib/crt1.o /opt/forte_6.0/WS6/lib/values-xa.o -Y P,/opt/forte_6.0/lib/rw7:/opt/forte_6.0/lib:/opt/forte_6.0/WS6/lib/rw7:/opt/forte_6.0/WS6/lib:/usr/ccs/lib:/usr/lib memtest.o -lCstd -lCrun -lgc_dbg -lm -lw -lcx -lc /opt/forte_6.0/WS6/lib/crtn.o >&/tmp/ld.24546.0.err
    /opt/forte_6.0/bin/../WS6/bin/c++filt -stderr </tmp/ld.24546.0.err
    Undefined               first referenced
    symbol                in file
    dlopen                             /opt/forte6.0/WS6/lib/libgc_dbg.a(dyn_load.o) (symbol belongs to implicit dependency /usr/lib/libdl.so.1)
    ld: fatal: Symbol referencing errors. No output written to memtest
    rm /tmp/ld.24546.0.err
    rm memtest.o
    rm /tmp/ccfe.24540.0.s
    </code>
    When I add <tt>-ldl</tt> to the command the binary is linked successfully but crashes on startup in a function named <tt>SymbolTable::lookupModuleByOrigin</tt>.
    What am I doing wrong? Perhaps something in my environment or our Forte6 installation could be the reason?
    Thanks,
    Adalbert Perbandt

    Problem is with 3.x version of compiler.
    So uninstall following packages:
    compat-gcc-c++
    compat-gcc
    compat-libstdc++-devel
    compat-libstdc++
    Then download following packages from Fedora Core 2:
    http://download.fedora.redhat.com/pub/fedora/linux/core/2/i386/os/Fedora/RPMS/compat-gcc-7.3-2.96.126.i386.rpm
    http://download.fedora.redhat.com/pub/fedora/linux/core/2/i386/os/Fedora/RPMS/compat-gcc-c++-7.3-2.96.126.i386.rpm
    http://download.fedora.redhat.com/pub/fedora/linux/core/2/i386/os/Fedora/RPMS/compat-libstdc++-7.3-2.96.126.i386.rpm
    http://download.fedora.redhat.com/pub/fedora/linux/core/2/i386/os/Fedora/RPMS/compat-libstdc++-devel-7.3-2.96.126.i386.rpm
    and install it. Now try to comile again.

  • Java JDBC Communication Link Failure

    Hi,
    I have a Java application which utilizes the JDBC mysql connector 5.1.6. It works great, and I am able to connect to my MySQL database just fine and execute queries perfectly.
    However, it seems that if my server idles for certain periods of time without issuing a command to the MySQL server (and this idle period seems to be variant; sometimes if it sites just 5 minutes I get this error, other times it has to idle for close to 25 minutes before it gives me this error):
    com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: Communications link failure
    Last packet sent to the server was 1493610 ms ago.Obviously the "... ms ago" part varies based on how long the server was idling.
    This is a particular problem for me because the purpose of my application is to be one part in more of an enterprise information system. So this connection to the database is intended to make an update every 25 minutes to update a user's session data in my database. Unfortunately, when idling for this long it will just error out.
    My temporary solution has been to catch this exception, reconnect, and re-issue the query which is working, but that's like putting a band-aid on a wound that needs stitches. The real problem is I have so many areas in my code where I execute commands that it would make it difficult to maintain if I had to use this Try-Catch method of reconnecting in each spot.
    Is there some timeout setting I need to set in MySQL or in the JDBC to stopt his error from happening? I have read the MySQL documentation and its timeout is already set to an hour so that shouldn't be the problem...
    Thanks!

    I searched for this on google:
    com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: Communications
    and here is a link that might help:
    http://forums.mysql.com/read.php?39,199085,204628#msg-204628
    I think the key to your problem is the last line in that link. In connection pooling, you should get a connection, use it, then close it as quickly as possible (ideally, all in the same function within try/catch/finally block) for each time you need to use a connection (hundreds of times within your application). I suspect you open a connection and keep it open with the anticipation that there is a performance penalty in alternatively opening and closing it hundreds of times. There is none. The act of getting and closing a connection from a connection pool is a lightweight operation (in terms of performance). I suggest going back and refactoring your code with the above in mind. That way, your connections will never time out (they are only open for a few milliseconds at a time).

  • CLI0108E Communication link failure. After clone machine

    AIX 5.3
    SAP R / 3 4.7 Enterprise 110
    DB2 9.5 fix pack 2
    We did a clone machine that already had SAP and DB2 9.5 installed and changed the host and ip.
    After adjustments sidadm user profiles, user db2prd and adjust db2conf password file, database and SAP initialize however, is occurring Dumps:.
    Database error text........: "CLI0108E Communication link failure.
    SQLSTATE=40003"  
    Previously the same dump occurred when accessed RZ10- import profile of active server. Once deleted entries in the tables  TPFET and TPFHT dump no longer occurs in RZ10.
    The dump occurs in certain situations such as: SE06-Data base or Data Migration Perform post-installation.After that the dump occurs and the following message appears: connection lost to database, session terminated and closes the connection to SAP.
    I thought about asking the customer to perform the clone in separate network with the same host or conduct a new HSC if no solution.
    I appreciate any help.
    Below are some logs:
    Fri Oct 14 19:19:26 2011
    C  *** ERROR in DB6Fetch[dbdb6.c, 3385] CON = 0 (BEGIN)
    C  &+     DbSlExeReadDB6( SQLFetch ): [IBM][CLI Driver] SQL1224N  The database manager is not able to accept new requests, h
    C  &+     as terminated all requests in progress, or has terminated your particular request due to an error or a force inter
    C  &+     rupt.  SQLSTATE=55032                                                                               
    C  &+                                                                               
    C  &+     SELECT * FROM "E070" WHERE NOT ( "TRKORR" LIKE ? ) AND "TRSTATUS" <> ? AND "TRFUNCTION" IN ( ? , ? , ? , ? , ? , ?
    C  &+      , ? )                                                                               
    C  &+       cursor type=NO_HOLD, isolation=UR, cc_release=NO, optlevel=5, degree=1, op_type=18, reopt=0                    
    C  &+       ABAP location info: 'SAPLSTRO', 1286                                                                           
    C  &+                                                                               
    C  &+     Input SQLDA:                                                                               
    C  &+                        1 CT=CHAR            T=VARCHAR         L=4     P=4     S=0   
    C  &+                        2 CT=CHAR            T=CHAR            L=1     P=1     S=0   
    C  &+                        3 CT=CHAR            T=CHAR            L=1     P=1     S=0   
    C  &+                        4 CT=CHAR            T=CHAR            L=1     P=1     S=0   
    C  &+                        5 CT=CHAR            T=CHAR            L=1     P=1     S=0   
    C  &+                        6 CT=CHAR            T=CHAR            L=1     P=1     S=0   
    C  &+                        7 CT=CHAR            T=CHAR            L=1     P=1     S=0   
    C  &+                        8 CT=CHAR            T=CHAR            L=1     P=1     S=0   
    C  &+                        9 CT=CHAR            T=CHAR            L=1     P=1     S=0   
    C  &+                                                                               
    C  &+     Input data:                                                                               
    C  &+     row 1: [ERR]       1 CHAR            I=4       "SAP%"
    C  &+                        2 CHAR            I=1       "R"
    C  &+                        3 CHAR            I=1       "C"
    C  &+                        4 CHAR            I=1       "K"
    C  &+                        5 CHAR            I=1       "L"
    C  &+                        6 CHAR            I=1       "R"
    C  &+                        7 CHAR            I=1       "S"
    C  &+                        8 CHAR            I=1       "T"
    C  &+                        9 CHAR            I=1       "W"
    C  &+                                                                               
    C  &+     Output SQLDA:                                                                               
    C  &+                        1 CT=CHAR            T=VARCHAR         L=20    P=20    S=0   
    C  &+                        2 CT=CHAR            T=CHAR            L=1     P=1     S=0   
    C  &+                        3 CT=CHAR            T=CHAR            L=1     P=1     S=0   
    C  &+                        4 CT=CHAR            T=VARCHAR         L=10    P=10    S=0   
    C  &+                        5 CT=CHAR            T=VARCHAR         L=4     P=4     S=0   
    C  &+                        6 CT=CHAR            T=VARCHAR         L=12    P=12    S=0   
    C  &+                        7 CT=CHAR            T=CHAR            L=8     P=8     S=0   
    C  &+                        8 CT=CHAR            T=CHAR            L=6     P=6     S=0   
    C  &+                        9 CT=CHAR            T=VARCHAR         L=20    P=20    S=0   
    C  &+                                                                               
    C  &+     ABAP location info 'SAPLSTRO', 1286                                                                               
    C  &+     SAP user 'PWBASIS', transaction code 'SE06'                                                                      
    C  &+                                                                               
    C  *** ERROR in DB6Fetch[dbdb6.c, 3385] (END)
    B  ***LOG BYM=> severe DB error -1224     ; work process in reconnect status [dbsh#4 @ 1127] [dbsh    1127 ]
    B  ***LOG BY4=> sql error -1224  performing FET on table E070       [dbtran#13 @ 7371] [dbtran  7371 ]
    B  ***LOG BY0=> SQL1224N  The database manager is not able to accept new requests, has terminated all requests in progress, or has terminated your particular request due to an error or a force interrupt.  SQLSTATE=55032 [dbtran#13 @ 7371] [dbtran  7371 ]
    B  dbtran ERROR LOG (hdl_dbsl_error): DbSl 'FET'
    ============================================
    C Fri Oct 14 19:20:18 2011
    C  *** ERROR in DB6Connect[dbdb6.c, 1482] CON = 0 (BEGIN)
    C  &+     DbSlConnectDB6( SQLConnect ): [IBM][CLI Driver] SQL1032N  No start database manager command was issued.  SQLSTATE=
    C  &+     57019                                                                               
    C  &+                                                                               
    C  &+                                                                               
    C  *** ERROR in DB6Connect[dbdb6.c, 1482] (END)
    C  *** ERROR => DbSlConnect to 'PRD' as 'sapprd' failed
    ==========================================
    db2diag.log
    2011-10-14-19.19.27.022877+000 E5735635A801       LEVEL: Critical
    PID     : 1233036              TID  : 5913        PROC : db2sysc 0
    INSTANCE: db2prd               NODE : 000
    EDUID   : 5913                 EDUNAME: db2pclnr (PRD) 0
    FUNCTION: DB2 UDB, base sys utilities, sqle_panic, probe:10
    MESSAGE : ADM14001C  An unexpected and critical error has occurred: "Panic".
              The instance may have been shutdown as a result. "Automatic" FODC
              (First Occurrence Data Capture) has been invoked and diagnostic
              information has been recorded in directory
              "/db2/PRD/db2dump/FODC_Panic_2011-10-14-19.19.26.809033/". Please
              look in this directory for detailed evidence about what happened and
              contact IBM support if necessary to diagnose the problem.
    2011-10-14-19.19.26.800536+000 I5720080A624       LEVEL: Severe
    PID     : 1233036              TID  : 14651       PROC : db2sysc 0
    INSTANCE: db2prd               NODE : 000         DB   : PRD
    APPHDL  : 0-44                 APPID: *LOCAL.db2prd.111014191834
    AUTHID  : SAPPRD 
    EDUID   : 14651                EDUNAME: db2agent (PRD) 0
    FUNCTION: DB2 UDB, buffer pool services, sqlbCleanupBeforeTerm, probe:837
    MESSAGE : ZRC=0x8602001A=-2046689254=SQLB_BADD "Bad Database, Can't flush"
              DIA8427C The database has been marked as being damaged.
    DATA #1 : String, 48 bytes
    A portion of SQLB termination processing failed.
    2011-10-14-19.19.26.801650+000 I5720705A430       LEVEL: Error
    PID     : 1233036              TID  : 5656        PROC : db2sysc 0
    INSTANCE: db2prd               NODE : 000
    EDUID   : 5656                 EDUNAME: db2pclnr (PRD) 0
    FUNCTION: DB2 UDB, data protection services, sqlpgild, probe:310
    RETCODE : ZRC=0x8610000D=-2045771763=SQLP_BADLOG "Log File cannot be used"
              DIA8414C Logging can not continue due to an error.
    2011-10-14-19.48.44.487238+000 E6321299A549       LEVEL: Severe
    PID     : 1019968              TID  : 258         PROC : db2wdog 0
    INSTANCE: db2prd               NODE : 000
    EDUID   : 258                  EDUNAME: db2wdog 0
    FUNCTION: DB2 UDB, base sys utilities, sqleWatchDog, probe:20
    MESSAGE : ADM0503C  An unexpected internal processing error has occurred.  ALL
              DB2 PROCESSES ASSOCIATED WITH THIS INSTANCE HAVE BEEN SHUTDOWN. 
              Diagnostic information has been recorded.  Contact IBM Support for
              further assistance

    Hi Shahin,
    At the time I did not find a solution, so I installed the R / 3 4.7 on a machine with the same host and then I did a homogeneous system copy.
    At the time I did not find a solution, so I installed the R / 3 4.7 on a machine with the same host and then I did a homogeneous system copy.
    Perhaps an export base correct the problem. I have not tried the time.
    If you find a solution, let us know.
    regards,
    Emerson

  • Fc2/y is down (Link failure: NOS received)

    Please Help
    UCSM : 1.4 (3l)
    Storage FC Ports : fc2/1, fc2/3, fc2/5
    error : fc2/5
    B(nxos)# sh interface fc 2/5
    fc2/5 is down (Link failure: NOS received)
    from UCSM
    fc port 5 on fabric interconnect B oper state:failed, reason:Link failure: NOS received
    disable and enable port
    error : fc2/5
    B(nxos)# sh interface fc 2/5
    fc2/5 is down (Link failure or not-connected)
    wahtis the root cause problem?
    Best regards

    Hello,
    NOS refers to "No operatioal sequence". Fibre channel has primitive seqences which are used to establish and maintain a link among the devices.
    During the initial login phase,
    1.Fiber channel switch sends a NOS signal
    2.HBA connected to it sends an "OLS (offline sequence) signal.
    3.Switch would send  a "Link reset"(LR)
    4.HBA responds with a "LRR (link reset response)"
    When a NOS received condition is met,
    •A signal loss or sync loss condition is detected.
    •The port is administratively shut down.
    •The port is operationally down.
    When the port status is in "link failure or not-connected" state, it means that the physical path is not completely active or no active signals has been sent. Check the cables/SFP's if pluged in properly and check the configuration (port type, speed and vsan settings) for further troubleshooting.

  • IBM Client Access ODBC Driver DB2/400 SQL7017 Unable to run statement with specified commit level #-7017

    Changed IBM As/400 system from V4R5 to V5R2 and now get this message when using Access to link to external database the same exact settings on everything I can determine on all computers. 
    IBM Client Access ODBC Driver DB2/400 SQL7017 Unable to run statement with specified commit level #-7017
    I have Commit immediate = *NONE in the Advanced Server Options in ODBC Data Source Administrator. It shows the AS/400 files in the Link Tables list and allows me to add it to the Access table objects, but when I try to open it in datasheet view I get that
    error.
    What am I missing?

    Ouch. That's a lot of paste...
    INFO: PATH = C:\oracle\product\10.2.0\client_2;C:\oracle\product\10.2.0
    \client_1;T:\SDCHS20N440\Oracle\agent10g\jlib;T:\SDCHS20N440
    \Oracle\agent10g\bin
    INFO: The flags set for this home (T:\SDCHS20N440\Oracle\agent10g) are:clean
    SEVERE: Abnormal program termination. An internal error has occured. Please
    provide the following files to Oracle Support : I wonder how "T:" is involved. Looks like you got a management agent on a network drive. If so, is this Home registered with the oraInventory on your machine? Can you try the same install on a machine without any previous Oracle software installed?

  • Fc port 47 on fabric interconnect A oper state: failed, reason: Link failure: OLS received

    Hi,
    this UCS is connected to a qlogics SAN Fabric. We can see the LUN in ESX 5, but can't write. If we want write something to the LUN, we get the error above. We know that the qlogic Fabric is not supported by UCS, but its NPIV and i have a similar Installation which is doing fine.
    Any Ideas?
    Thanks, Marco

    Hello,
    NOS refers to "No operatioal sequence". Fibre channel has primitive seqences which are used to establish and maintain a link among the devices.
    During the initial login phase,
    1.Fiber channel switch sends a NOS signal
    2.HBA connected to it sends an "OLS (offline sequence) signal.
    3.Switch would send  a "Link reset"(LR)
    4.HBA responds with a "LRR (link reset response)"
    When a NOS received condition is met,
    •A signal loss or sync loss condition is detected.
    •The port is administratively shut down.
    •The port is operationally down.
    When the port status is in "link failure or not-connected" state, it means that the physical path is not completely active or no active signals has been sent. Check the cables/SFP's if pluged in properly and check the configuration (port type, speed and vsan settings) for further troubleshooting.

  • MDS 9148 NX-OS 5.0(1a) Link failure Problem

    Hi all,
    I'm finding the following problem on my 2 MDS9148 switches.
    2012 May  7 14:15:54 SAN01 %PORT-4-IF_SFP_WARNING: Interface fc1/7, Low Rx Power Warning  BK01
    2012 May  7 14:15:54 SAN01 %PORT-3-IF_SFP_7ALARM: Interface fc1/7, Low Rx Power Alarm  BK01
    And finally the FC interfaces go down. We checked the fiber cable to be sure that it is not a physical issue and the fiber cables are ok.
    This happens with fc1/1, 1/3, 1/4 and several more.
    Does anyone have an idea why this could be happening and what the error might be?
    Your help will be much appreciated.
    Thanks in advance,
    Kind regards

    Krun_shah
    Seems that the other post has not a good layout.
    Here it is: THe error:
    2012 Sep  4 09:34:43 SAN-01 %PORT-2-IF_DOWN_LINK_FAILURE: %$VSAN 2%$ Interface fc1/1 is down (Link failure)  LTO3
    2012 Sep  4 09:34:44 SAN-01 %PORT-2-IF_DOWN_LINK_FAILURE: %$VSAN 2%$ Interface fc1/1 is down (Link failure)  LTO3
    2012 Sep  4 09:34:44 SAN-01 %PORT-2-IF_DOWN_LINK_FAILURE: %$VSAN 2%$ Interface fc1/5 is down (Link failure)  LTO3
    2012 Sep  4 09:35:31 SAN-01 %PORT-2-IF_DOWN_LINK_FAILURE: %$VSAN 2%$ Interface fc1/5 is down (Link failure)  LTO3
    2012 Sep  4 09:35:31 SAN-01 %PORT-5-IF_UP: %$VSAN 2%$ Interface fc1/1 is up in mode FL  LTO3
    2012 Sep  4 09:35:33 SAN-01 %PORT-5-IF_UP: %$VSAN 2%$ Interface fc1/5 is up in mode FL  LTO3
    2012 Sep  4 09:36:57 SAN-01 %PORT-4-IF_SFP_WARNING: Interface fc1/1, Low Rx Power Warning  LTO3
    2012 Sep  4 09:36:57 SAN-01 %PORT-4-IF_SFP_WARNING: Interface fc1/5, Low Rx Power Warning  LTO3
    2012 Sep  4 09:36:57 SAN-01 %PORT-3-IF_SFP_ALARM: Interface fc1/5, Low Rx Power Alarm  LTO3
    2012 Sep  4 09:46:58 SAN-01 %PORT-4-IF_SFP_WARNING: Interface fc1/1, Low Rx Power Warning cleared  LTO3
    2012 Sep  4 09:46:58 SAN-01 %PORT-3-IF_SFP_ALARM: Interface fc1/1, Low Rx Power Alarm cleared  LTO3
    2012 Sep  4 09:46:58 SAN-01 %PORT-4-IF_SFP_WARNING: Interface fc1/5, Low Rx Power Warning cleared  LTO3
    2012 Sep  4 09:46:58 SAN-01 %PORT-3-IF_SFP_ALARM: Interface fc1/5, Low Rx Power Alarm cleared 
    The fc1/1 and fc1/5 ports are experiencing the same problem as fc1/7 so I am pasting the show command output for those ports.
    The fc1/1 and fc1/5 are not ISL ports I believe. You mean ISL as the trunking protocol, right?
    Here it is the config for both ports.
    interface fc1/1
      switchport description LTO3
      port-license acquire
      no shutdown
    interface fc1/5
      switchport description LTO3
      port-license acquire
      no shutdown
    WE have connected to those ports a drive that is used by a backup robot.
    Here are the ouput for the show commands you asked.
    sh int fc1/1 counters  details
    fc1/1
          4417757720 frames, 5859624695228 bytes received
          0 class-2 frames, 0 bytes received
          0 class-2 discards
          0 F_BSY frames, 0 F_RJT frames
              generated against class-2 frames
          0 port reject frames
          4417757720 class-3 frames, 5859624695228 bytes received
          0 class-f frames, 0 bytes received
          0 discards, 0 errors received
          0 discards, 117 errors transmitted
          100604456388 frames, 207142346384892 bytes transmitted
          0 class-2 frames, 0 bytes transmitted
          100604456388 class-3 frames, 207142346384892 bytes transmitted
          0 class-3 frames discarded
          0 class-f frames, 0 bytes transmitted
          0 class-f frames discarded
          0 multicast packets received, 0 transmitted
          0 broadcast packets received, 0 transmitted
          4417756190 unicast packets received, 100611090558 transmitted
          85 link failures, 82 sync losses,       77 signal losses
          0 primitive sequence protocol errors
          163601 invalid transmission words
          0 invalid CRCs, 0 Delimiter Errors
          0 address identifier errors
          0 link reset protocol errors received
          0 link reset protocol errors transmitted
          0 Offline Sequence errors received
          173 Offline Sequence errors transmitted
          0 frames received that are shorter than
              the minimum allowable frame length
              regardless of the CRC error
          0 frames received that are longer than
              the maximum frame length and also have a
              CRC error
          0 waits due to lack of transmit credits
          0 frames received with length greater
              than what was agreed to in FLOGI/PLOGI
          0 frames received with length less than
              the minimum indicated by the frame header
          0 link reset responses received
          0 link reset responses transmitted
          0 non-operational sequences received
          88 non-operational sequences transmitted
          0 fragmented frames received
          0 frames received with EOF aborts
          0 unknown class frames received
          0 8b10b disparity errors
          117 frames discarded
          0 Exchange Link Parameters switch fabric
              internal link service request failures
          110542953 transitions of BB credit out of zero state
          0 transitions of BB credit to zero state
          0 Enhanced Inter Switch Link (EISL) frames
              discarded
          0 framing errors
          0 F8 type LIP sequence errors received
          0 F8 type LIP sequence errors issued
          193 Non F8 type LIP sequence errors received
          173 Non F8 type LIP sequence errors issued
    SAN-01# sh int fc 1/1 transceiver details
    fc1/1 sfp is present
        Name is CISCO-AVAGO    
        Manufacturer's part number is SFBR-5780APZ-CS2
        Revision is G2.3
        Serial number is AGD143284VM    
        FC Transmitter type is short wave laser w/o OFC (SN)
        FC Transmitter supports short distance link length
        Transmission medium is multimode laser with 62.5 um aperture (M6)
        Supported speeds are - Min speed: 2000 Mb/s, Max speed: 8000 Mb/s
        Nominal bit rate is 8500 Mb/s
        Link length supported for 50/125mm fiber is 50 m
        Link length supported for 62.5/125mm fiber is 20 m
        Cisco extended id is unknown (0x0)
        No tx fault, no rx loss, in sync state, diagnostic monitoring type is 0x68
        SFP Diagnostics Information:
                                         Alarms                  Warnings
                                    High        Low         High          Low
      Temperature  34.66 C         75.00 C     -5.00 C     70.00 C        0.00 C
      Voltage       3.27 V          3.63 V      2.97 V      3.46 V        3.13 V
      Current       7.09 mA         8.50 mA     2.00 mA     8.50 mA       2.00 mA
      Tx Power     -2.91 dBm        1.70 dBm  -14.00 dBm   -1.30 dBm    -10.00 dBm
      Rx Power     -6.76 dBm        3.00 dBm  -17.30 dBm    0.00 dBm    -13.30 dBm
      Transmit Fault Count = 0
      Note: ++  high-alarm; +  high-warning; --  low-alarm; -  low-warning
    SAN-01# sh int fc1/5 counters  details
    fc1/5
          4486944237 frames, 5759105445416 bytes received
          0 class-2 frames, 0 bytes received
          0 class-2 discards
          0 F_BSY frames, 0 F_RJT frames
              generated against class-2 frames
          0 port reject frames
          4486944237 class-3 frames, 5759105445416 bytes received
          0 class-f frames, 0 bytes received
          0 discards, 0 errors received
          0 discards, 2 errors transmitted
          108664953452 frames, 223758725747704 bytes transmitted
          0 class-2 frames, 0 bytes transmitted
          108664953452 class-3 frames, 223758725747704 bytes transmitted
          0 class-3 frames discarded
          0 class-f frames, 0 bytes transmitted
          0 class-f frames discarded
          0 multicast packets received, 0 transmitted
          0 broadcast packets received, 0 transmitted
          4486942834 unicast packets received, 108671587794 transmitted
          63 link failures, 62 sync losses,       6 signal losses
          0 primitive sequence protocol errors
          124 invalid transmission words
          0 invalid CRCs, 0 Delimiter Errors
          0 address identifier errors
          0 link reset protocol errors received
          0 link reset protocol errors transmitted
          0 Offline Sequence errors received
          129 Offline Sequence errors transmitted
          0 frames received that are shorter than
              the minimum allowable frame length
              regardless of the CRC error
          0 frames received that are longer than
              the maximum frame length and also have a
              CRC error
          0 waits due to lack of transmit credits
          0 frames received with length greater
              than what was agreed to in FLOGI/PLOGI
          0 frames received with length less than
              the minimum indicated by the frame header
          0 link reset responses received
          0 link reset responses transmitted
          0 non-operational sequences received
          66 non-operational sequences transmitted
          0 fragmented frames received
          0 frames received with EOF aborts
          0 unknown class frames received
          0 8b10b disparity errors
          2 frames discarded
          0 Exchange Link Parameters switch fabric
              internal link service request failures
          294071266 transitions of BB credit out of zero state
          0 transitions of BB credit to zero state
          0 Enhanced Inter Switch Link (EISL) frames
              discarded
          0 framing errors
          0 F8 type LIP sequence errors received
          0 F8 type LIP sequence errors issued
          134 Non F8 type LIP sequence errors received
          129 Non F8 type LIP sequence errors issued
    SAN-01# sh int fc 1/5 transceiver details
    fc1/5 sfp is present
        Name is CISCO-AVAGO    
        Manufacturer's part number is SFBR-5780APZ-CS2
        Revision is G2.3
        Serial number is AGD143284VS    
        FC Transmitter type is short wave laser w/o OFC (SN)
        FC Transmitter supports short distance link length
        Transmission medium is multimode laser with 62.5 um aperture (M6)
        Supported speeds are - Min speed: 2000 Mb/s, Max speed: 8000 Mb/s
        Nominal bit rate is 8500 Mb/s
        Link length supported for 50/125mm fiber is 50 m
        Link length supported for 62.5/125mm fiber is 20 m
        Cisco extended id is unknown (0x0)
        No tx fault, no rx loss, in sync state, diagnostic monitoring type is 0x68
        SFP Diagnostics Information:
                                         Alarms                  Warnings
                                    High        Low         High          Low
      Temperature  36.53 C         75.00 C     -5.00 C     70.00 C        0.00 C
      Voltage       3.26 V          3.63 V      2.97 V      3.46 V        3.13 V
      Current       7.08 mA         8.50 mA     2.00 mA     8.50 mA       2.00 mA
      Tx Power     -2.72 dBm        1.70 dBm  -14.00 dBm   -1.30 dBm    -10.00 dBm
      Rx Power     -3.94 dBm        3.00 dBm  -17.30 dBm    0.00 dBm    -13.30 dBm
      Transmit Fault Count = 0
      Note: ++  high-alarm; +  high-warning; --  low-alarm; -  low-warning
    thanks in advance,
    Fernando

Maybe you are looking for