Imperva Cyber Community

communities_1.jpg
 View Only
  • 1.  Error Ora-12154 when try delete license

    Posted 20 days ago
    Edited by Aloysius Erwin 18 days ago
      |   view attached

    Hi All,

    Due to certain circumstances, I need to delete existing license file on MX .

    Support asked me to do below procedure 

    1. Stop the server (impctl server stop)
    2. (recommended) Take a Full export of the MX without the Alerts and save it on a different machine. Use full_expimp.sh to do a export.
    3. Log in to the console with root user and perform the following commands:
      1. su - oracle
      2. sqlplus secure/<password>
      3. delete from CONF_CS_LICENSE_MODULES;
      4. delete from CONF_GW_LICENSE_MODULES;
      5. delete from CONF_LICENSE_FILES;
      6. delete from LIC_LICENSE_CONNECTIONS;  (* relevant only from version 7.5 and up)
      7. commit;
      8. exit
    4. exit
    5. impctl server start
    6. Once the server is completely up and running, access the web interface. At this point you should the server will ask you to upload a new license.

    when I tried execute  sqlplus secure/password>  , I got error Ora-12514  TNS:could not resolve the connect identifier specified. 

    tried do   sqlplus / as sysdba   and do delete from CONF_CS_LICENSE_MODULES;  it wrote  no table exist. 

    how should I fix this issue? 

    I use MX / GW version 14.19.1.40 

    --------------------------------------

    updated 25 Feb 2026

    Support replied email after 1 week. 

    error ORA-12154: TNS: could not resolve the connection identifier specified.

    This is due to system/secure password used the special character @ inside.

    Working Around : Don’t use @ for system and secure passwords

    case closed

    thank you


    #DatabaseActivityMonitoring

    ------------------------------
    Aloysius Erwin
    Solutions Engineer
    PT Exclusive Networks Indonesia
    Jakarta
    ------------------------------



  • 2.  RE: Error Ora-12154 when try delete license

    Posted 10 days ago

    Hi Aloysius,

    I noticed your question had not be answered so did some digging internally.

    I understand that this specific case required support and that due to its urgency you were able to implement a successful work around.

    Thanks so much for posting. I look forward to your next post. :-)



    ------------------------------
    Sarah Lamont
    Digital Community Manager
    ------------------------------