ORA-01830/ora-1839

Similar Questions

• Error ORA-01840 on insert object browser hollow line

  Dear Oracle Community,
  
  I get ORA-01840: not long enough for date input format error when I try to insert a row with the value of date 24 May 10 with my object browser.
  
  It's the column causing the problem:
  Name of column. Data type | Nullable | By default | Primary key
  SIGNUPDATE | DATE | Don't | - | -
  
  Now it will look like I use the incorrect date format, so I googled and found that I should use the following query to check the correct date format that uses my database.
  Select * from nls_session_parameters where parameter = "NLS_DATE_FORMAT;
  
  This refers to the format DD-MON-RR so I think that I am inserting the correct date format.
  What I am doing wrong?
  
  I already tried to insert with the following formats and tried to replace the - sign with the / / sign.
  DD-MON-RR
  LUN-JJ-AA
  DD-MON-YYYY
  
  I also tried to use the SYSDATE is in the format DD-MON-RR ditch the SQL command line.
  
  I feel like a fool, this should be simple right?
  
  Help me please here it is frustrating, thanks in advance.
  
  Nijman J

  using the SYSDATE is in the format DD-MON-RR ditch the SQL command line

  Try sqlplus:
  insert into ( [,...]) values (sysdate [,...]);

  To get a date value sysdate added. Or specify the format with a to_date expression string:
  insert into ( [,...]) values (to_date (24-May-10', 'Dd-mon-yy') [,...]);

  The engine is not fussy about agree separators with the format string, the most of any character instead of the '-' dash is acceptable.

  Now to get an ora-1840 out of the browser of the object (Table/data/insert a line), I'm not having any luck trying to duplicate that. With the default nls_date_format 'DD-MON-YY', trying even bad dates (e.g. 30-Feb.-10 or 30-Feb.-2010 or even 31-apr-10), he's either an ora-1839: date not valid for the specified month or with a four-digit year, he gives an ora-1830: date format picture ends before converting all of the input string.

  Any RDBMS present programmers with challenges of type date and datetime, this isn't just something oracle-frustration ;)

• ORA-01830: date format

  Hi all

  in 10.2.0.3

  I have run the following query:

  Select completion_time from V$ BACKUP_DATAFILE where creation_time < sysdate-10;

  12/06/2013-12:39:34

  12/06/2013-12:35:20

  But when executing:

  Select file # completion_time, blocks, block_size in V$ BACKUP_DATAFILE where completion_time > (select to_char (sysdate - 6/24, ' DD/MM/YY HH24:mi:ss') of double)

  I have:

  ORA-01830: date format picture ends before converting all of the input string

  Thanks for help.

  > where completion_time > (select to_char (sysdate - 6/24, ' DD/MM/YY HH24:mi:ss') of double)

  Why you convert sysdate to a string? (and why are you selecting in double?)

  Your first example he was entitled.

  Did you mean this: where completion_time > sysdate - 6/24;

• Validate the XML: DateTime-&gt; ORA-01830 / 01858

  Hello
  
  I'm trying to parse an XML document that contains an element which is defined as DateTime

  <CreDtTm>2012-06-02T09:30:47.000Z</CreDtTm>

  The xsd is as follows

  <xs:element name="CreDtTm" type="ISODateTime"/>
  ...
  <xs:simpleType name="ISODateTime">
    <xs:restriction base="xs:dateTime"/>
  </xs:simpleType>

  For me the format looks OK, but I get

  ORA-01830: date format picture ends before converting entire input string

  I found http://stackoverflow.com/questions/6370035/why-dbms-xmlschema-fails-to-validate-a-valid-xsdatetime/6382096#6382096
  and changed the schema:

  <xs:simpleType name="ISODateTime" xdb:SQLType="TIMESTAMP WITH TIME ZONE">

  Now, I get

  ORA-01858: a non-numeric character was found where a numeric was expected

  So I tried

  ALTER SESSION SET NLS_TIMESTAMP_TZ_FORMAT='yyyy-mm-dd"T"hh24:mi:ss.ff3"Z"';

  and tested

  select systimestamp from dual;
  
  SYSTIMESTAMP
  ----------------------------------------
  2012-07-27T10:52:05.860Z

  The exact format, but still ORA-01858.
  
  Validation is performed with

  DECLARE
    xmldoc XMLTYPE;
  DECLARE
    xmldoc XMLTYPE;
  BEGIN
      xmldoc := XMLTYPE(q'[<?xml version="1.0" encoding="UTF-8"?>
        ...
        <CreDtTm>2012-06-02T09:30:47.000Z</CreDtTm>
        ...]');
      xmldoc := xmldoc.createSchemaBasedXML('http://...xsd');
      XMLTYPE.schemaValidate(xmldoc);
  END;

  Anyone know where I am going wrong?
  

  select * from v$version;
  
  BANNER
  --------------------------------------------------------------------------------
  Oracle Database 11g Enterprise Edition Release 11.2.0.2.0 - 64bit Production
  PL/SQL Release 11.2.0.2.0 - Production
  CORE    11.2.0.2.0      Production
  TNS for HPUX: Version 11.2.0.2.0 - Production
  NLSRTL Version 11.2.0.2.0 - Production

  Concerning
  Marcus
  
  Published by: Marwim on 27.07.2012 11:45
  Addition of the db version

  Hi Marcus,

  This one is interesting.
  I had already implemented my own example shortly before posting your own, then here's something that works for me:

  BEGIN
  
    dbms_xmlschema.registerSchema(
      schemaURL => 'test_ts.xsd'
    , schemaDoc => 
  
    '
  
    
    
      
    
  '
  
    , local => true
    , genTypes => false
    , genTables => false
    , enableHierarchy => dbms_xmlschema.ENABLE_HIERARCHY_NONE
    );
  
  END;
  /
  

  SQL> DECLARE
    2    doc xmltype := xmltype('2012-06-02T09:30:47.000Z', 'test_ts.xsd');
    3  BEGIN
    4    doc.schemaValidate();
    5  END;
    6  /
  DECLARE
  *
  ERROR at line 1:
  ORA-30992: error occurred at Xpath /CreDtTm[@SYS_XDBBODY$]
  ORA-01858: a non-numeric character was found where a numeric was expected
  ORA-06512: at "SYS.XMLTYPE", line 354
  ORA-06512: at line 4
  

  OK, same error so far.

  SQL> REM : change from ", " to ".,"
  SQL> ALTER SESSION SET nls_numeric_characters = '.,';
  
  Session altered.
  
  SQL> DECLARE
    2    doc xmltype := xmltype('2012-06-02T09:30:47.000Z', 'test_ts.xsd');
    3  BEGIN
    4    doc.schemaValidate();
    5  END;
    6  /
  
  PL/SQL procedure successfully completed.
  

  Now it's working.

  I know that there is an implicit conversion happening in addition to automatic mapping "dateTime"--> 'TIMESTAMP WITH time ZONE'.
  Documentation, although not very clear, seems to hint in that direction:

  With the help of Z back to indicate the time zone UTC

  XML Schema allows the time zone specified under Z, component to indicate the UTC time zone. When a leaking Z value is stored in a SQL TIMESTAMP WITH time ZONE TIMES column, the time zone is actually stored as + 00:00. Thus, the value retrieved contains the leak + 00:00, not the original Z. For example, if the value in the input XML document is 1973-02-12 T 13: 44:32Z, the output is 1973-02 - 12 T 13: 44:32.000000 + 00:00.

  So I think that Oracle is attempting to expand "2012-06 - 02T 09: 30:47.000Z" at "2012-06 - 02 T 09: + 00:00 30:47.000000"but relying on the NLS configuration session to determine the decimal separator used in the fractional part of timestamp.»

• Error ORA-01830 drives me crazy

  I've not found anything relevant online to my question so I'll try here. To set this up, I'm still in the learning I'll phase of Oralce, so be gentle please.
  
  I run this query:
  
  Update fascor_load
  Set order_status_id = 18
  where load_date < to_date('06-APR-01','DD-MON-YY');.
  
  He has in turn triggers:
  
  create or replace
  relaxation Fascor_Load_BUR
  before the update on Fascor_Load
  for each line
  
  declare
  closed whole;
  Date of Current_Date_Time;
  
  Start
  Select order_status_id from firm order_status where description = "CLOSED";
  Select to_char (sysdate,' HH24 LUN-JJ-AA "") in the double Current_Date_Time;
  
  If: old. Order_Status_ID <>: new. Order_Status_ID and
  : new. Order_Status_ID = closed and
  : new. Load_Completion_Date is null then
  
  -Insert Current Date/time in the field of Load_Completion_Date
  : new. Load_Completion_Date: = Current_Date_Time;
  end if;
  end;
  
  
  When you run the query, I get:
  
  
  ************************************************************
  Error from the 1 in the command line:
  Update fascor_load
  Set order_status_id = 18
  where load_date < to_date('06-APR-01','DD-MON-YY')
  Error report:
  SQL error: ORA-01830: date format picture ends before converting all of the input string
  ORA-06512: at "EIS_EMERY. FASCOR_LOAD_BUR', line 7
  ORA-04088: error during execution of trigger ' EIS_EMERY. FASCOR_LOAD_BUR'
  01830 00000 - "date format picture ends before converting all of the input string.
  * Cause:
  * Action:
  *************************************************************
  
  Someone has ideas on what exactly the cause this problem? I thought that perhaps that is the data type of Load_Completion_Date, which is of type 'Date', so I dropped the column and then tried to add it again but this time by putting a mask on it, but it would not get in shape the type date when adding the column.
  
  I'm lost on this and it seems to simple.

  927300 wrote:
  For me, the result is:

  18 APRIL 12

  Select TO_CHAR (sysdate,'YYYY-MM-DD HH24:MI:SS) twice;

  do high instead
  It is strictly a matter of presentation of data; also known as the formatting!

• sqlldr problem ORA-ORA-01830

  Well, I'm in the process of transferring data between sql server 2000 to oracle 10 g on windows.
  Here are the steps that I m that follows.
  
  1. export table to file MS-ACCESS (.mdb) via ODBC.
  2. make a file to load in the data base of control.
  3. with the help of sqlldr to load data
  4 but when loading I get this error ORA-01830 outside the date column...!
  
  If the question would be demand I could use the to_date function...
  
  But how to solve the problem with sql loader...!

  You can apply SQL functions for data entry fields.
  See more here:
  http://download.Oracle.com/docs/CD/B19306_01/server.102/b14215/ldr_field_list.htm#i1008150

• ORA-01830 during an attempt of incomplete recovery

  Hi guys,.
  
  I practice the incomplete recovery but my RMAN script fails with the following error:
  ORA-01830: date format picture ends before converting all of the input string
  
  Here's the RMAN script
  
  RUN
  {
  May 7, 2010 until 05:00 ";
  restore the database;
  recover the database;
  ALTER database open resetlogs;
  }
  
  My NLS_DATE_FORMAT has the value
  * # env | grep-i nls *.
  * # NLS_DATE_FORMAT = HH24:MI:SS * MON-DD-YYYY
  
  Linux x 86, Oracle 10.2.0.4

  In your case, case issues (my output is in windows, but should be the same on linux)

  SQL> alter session set nls_date_format='DD-MON-YYYY HH24:MI:SS';  -- sqlplus can handle uppercase
  
  Session altered.
  
  SQL> select sysdate from dual;
  
  SYSDATE
  --------------------
  07-MAY-2010 22:27:14
  
  ### but your environment is less forgiving  ###
  
  C:\Documents and Settings\User>set nls_date_format=DD-MON-YYYY HH24:MI:SS
  
  C:\Documents and Settings\User>rman target /
  
  Recovery Manager: Release 10.2.0.1.0 - Production on Fri May 7 22:24:47 2010
  
  Copyright (c) 1982, 2005, Oracle.  All rights reserved.
  
  connected to target database: PTS (DBID=774850390)
  
  RMAN> RUN
  2> {
  3> set until time '07-MAY-2010 05:00:00';
  4> }
  
  executing command: SET until clause
  using target database control file instead of recovery catalog
  RMAN-00571: ===========================================================
  RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
  RMAN-00571: ===========================================================
  RMAN-03002: failure of set command at 05/07/2010 22:25:09
  ORA-01830: date format picture ends before converting entire input string
  

  Now let's see what happens when I put the NLS_DATE_FORMAT correctly:

  C:\Documents and Settings\User>set nls_date_format=DD-MON-YYYY hh24:mi:ss
  
  C:\Documents and Settings\User>rman target /
  
  Recovery Manager: Release 10.2.0.1.0 - Production on Fri May 7 22:25:36 2010
  
  Copyright (c) 1982, 2005, Oracle.  All rights reserved.
  
  connected to target database: PTS (DBID=774850390)
  
  RMAN> RUN
  2> {
  3> set until time '07-MAY-2010 05:00:00';
  4> }
  
  executing command: SET until clause
  using target database control file instead of recovery catalog
  

  Now, usually when I write RMAN scripts I'll put the nls_date_format there it will always be good for the rman session:

  run {
  set until time "to_date('07-MAY-2010 05:00:00','dd-mm-yyyy hh24:mi:ss')";
  }
  

• ORA-01830: date format picture ends before converting all of the input string

  Hi exprets. I support to the top of my operation backupset dissertation I get this error. I am looking for this error on google, they say this nls_Date_format problem. But I have set up a format and try again I encounter the same error. When I look at the new location, I see my data file backup but backup control files is not there. could someone tell me please what is the problem with that?

  

  try to set the parameter as follows: export NLS_LANG = AMERICAN_AMERICA. UTF8

• get the ora-01830, but cannot say what I'm doing wrong

  Hi, Oracle 11g R2.

  Could someone help me understand what I'm doing wrong in following select clause? I'm trying to convert the difference in seconds to hh.

  ISN.snapshot_ts and iobd.bd_handshake_ts are TIMESTAMP (6) WITH ZONE SCHEDULE

  Select to_date ((to_date (to_char (isn. )))) snapshot_ts , 'HH24:MI:SS DD/MM/YYYY'), ' MM/DD/YYYY HH24:MI:SS')

  - to_date (to_char (iobd. )) bd_handshake_ts , 'MM/DD/YYYY HH24:MI:SS'), 'MM/DD/YYYY HH24:MI:SS'))*60*60*24, 'sssss')

  Hello

  Back-and-forth conversion as

  TO_DATE (to_char)

  are almost never necessary in Oracle.  There are a lot of built-in functions and features that make everything you need more simply.

  If you subtract one TIMESTAMP on the other, the result is an INTERVAL DAY TO SECOND.

  If you view an INTERVAL DAY TO SECOND, it is formatted as

  + 00:01:10.879000 000000000

  which is what you want.  In fact, it's what you want and then some others, which can be a problem for you.  If you are certain that the difference will be less than 24 hours, you can display the number of days in the beginning, and you're neither to display fractions of a second at the end.  In this case, you can convert the INTERVAL DAY TO SECOND string and then use SUBSTR (or similar) to get exactly the parts you want.

  Try something like:

  SELECT isn.snapshot_ts - iobd.bd.handshake_ts AS diff

  ...

  If this isn't what you want (or close enough) then after a small example of data (CREATE TABLE and INSERT statements) and the accurate results you want from these sample data.

  Check out the Forum FAQ: Re: 2. How can I ask a question on the forums?

• ORA-30992: an error has occurred to Xpath ready, CstmrCdtTrfInitn, GrpHdr, CreDtTm

  Hi all

  I get this error when my XML with an XSD validation using Oracle

  XMTYPE variable.schemavalidate ();

  ORA-30992: an error has occurred to Xpath ready, CstmrCdtTrfInitn, GrpHdr, CreDtTm

  ORA-01830: date format picture ends before converting all of the input string

  I have the following XML generated which is having an element with time zone time-stamped in it.

  Total on the XML data:

  < TransactionFile CreationDate = "" 2013-09 - 02T 16: 47:32 + 01:00 "entity"TEST"= >"

  I'm against an XSD validation then that apply to a style sheet and using Oracle XMLTRANSFORM

  The stylesheet has the following code (code XSLT):

  "< CreDtTm > < xsl: value-of select="@CreationDate "/ > < / CreDtTm >

  The XML is properly validated and transformed in the final XML output, but for some reason it adds any fraction to my such date as displayed below:

  < CreDtTm > 2013 - 09 - 05T 16: 40:44.000000 + 01:00 < / CreDtTm >

  I'm finally validate this output with a predefined standard XSD, where the CredtTm is defined as a datetime variable

  < xs: element name = "CreDtTm" type = "ISODateTime" / >

  ISODateTime is of type datetime

  < xs:simpleType name = "ISODateTime" >

  < xs:restriction base = "XS: DateTime" / >

  < / xs:simpleType >

  Thanks for reading so far. Near here the real problem

  I'm posting this in my Oracle pakaged procedure, using the v_pain_xmldata.schemavalidate ();   (variable v_pain_xmldata is an XMLTYPE variable)

  During the validation of the XML with this XSD it fails with the above error

  Can someone let me know why it's a failure? Because we have the final zone as in my XML output format in the w3school standard

  http://www.w3schools.com/schema/schema_dtypes_date.asp

  I tried different dates hardcoing in my XML final to see which element in the date is a failure and here are the results. I think that when I add the minus sign hrs it is a failure

  2013-09 - 02T 16: does not work 47:32 + 01:00 -
  2013-09 - 02T 16: 47:32 - does not work 01:00 -
  2013-09-02 16:47:32 - does not work

  2013-09-02 - works
  2013-09 - 02T 16: 47:32 - works
  2013-09 - 02T 16: 47:32.000000 - works

  I'm using Oracle Database 11 g Enterprise Edition Release 11.2.0.3.0 - 64 bit Production

  
  For the record, I can't edit the XSD to add anything into it like that

  < xdb:SQLType XS: attribute = "TIMESTAMP WITH TIME ZONE' name ="CreationDate"type =" xs: DateTime "use ="required"/ >"

  As this is a standard XSD SEPA provided by the customer and therefore no changes can be made for her.

  I have only option for me is to modify the stylesheet to probably enter a format to convert the date in datetime format, however, the above generated output is a valid datetime format.

  Any question, please get back to me. Would appreciate any help on getting this problem sorted.

  Thanks in advace.

  What is this parenthesis for?

• ORA-01830Date end of photo format before converting all of the input string

  Hi guys,.
  
  We have two env db a dev and AQ. Both the envs are running on the same version of database and in both the setting nls_date_format envs are the same and they are 'DD-MON-YY' format only. But when I execute the same statement immediately following my dev env is fetching data appropriate without any problem but my env qa is any mistake on the mentioned error.
  
  I enclose the suite that I use
  
  SELECT TPTRJO1. JOURNAL_ENTRY_ID
  OF TRANSACTION_JOURNAL TPTRJO1,.
  JOURNAL_CASH_DRAWER TPJCD1
  WHERE (TPJCD1. CASH_DRAWER_ID = 5010639.0)
  AND (TPJCD1. DRAWER_SEQ = 5.0)
  AND (TPJCD1. CASH_DRAWER_DATE = TO_DATE ('2011-09-13 00:00:00 ', 'yyyy-MM-dd'))
  
  AND (TPTRJO1. JOURNAL_ENTRY_ID = TPJCD1. JOURNAL_ENTRY_ID)
  AND (TPTRJO1. TRANSACTION_ID = 595,0)
  
  However, according to the logic, it should error in both the envs due date format and the actual data used in the entry.
  
  What would be the possible difference between the envs db towing?
  
  Please, share your ideas.
  Any suggestions are appreciated.
  
  Thank you and waiting for an early response

  I assume that you have given in your dev environment.
  If there is a record with TPJCD1. CASH_DRAWER_ID = 5010639.0,
  the expression ' TO_DATE ('2011-09-13 00:00:00 ', 'yyyy-MM-dd').
  will never be evaluated.

  Here is my test scenario where '1 = 0' prevents the date under evaluation:

  SQL>SELECT *
    2    FROM all_objects
    3   WHERE created > TO_DATE('2011-09-13 00:00:00', 'yyyy-MM-dd');
   WHERE created > TO_DATE('2011-09-13 00:00:00', 'yyyy-MM-dd')
                           *
  ERROR at line 3:
  ORA-01830: date format picture ends before converting entire input string
  
  SQL>
  SQL>SELECT *
    2    FROM all_objects
    3   WHERE 1 = 0 AND created > TO_DATE('2011-09-13 00:00:00', 'yyyy-MM-dd');
  
  no rows selected
  

  URS

• ORA-12012: error on auto work 49580

  the notes of any idea or metalink #s I should check for this problem? nothing works on the side apps...
  
  ORA-12012: error on auto work 49580
  ORA-01830: date format picture ends before converting all of the input string
  SAM 7 Mar 19:02:04 2009
  Errors in the /oracle/admin/insp/bdump/insp_j001_1454110.trc file:
  ORA-12012: error on auto run 49581 work
  ORA-01830: date format picture ends before converting all of the input string
  SAM 7 March 19:06:06 2009
  Errors in the /oracle/admin/insp/bdump/insp_j001_1548452.trc file:
  ORA-12012: error on auto run 49581 work
  ORA-01830: date format picture ends before converting all of the input string
  SAM 7 March 19:06:06 2009
  Errors in the /oracle/admin/insp/bdump/insp_j000_1667148.trc file:
  ORA-12012: error on auto work 49580
  ORA-01830: date format picture ends before converting all of the input string
  SAM 7 19:14:09 Mar 2009
  Errors in the /oracle/admin/insp/bdump/insp_j000_1650760.trc file:
  ORA-12012: error on auto work 49580
  ORA-01830: date format picture ends before converting all of the input string
  SAM 7 19:14:09 Mar 2009
  Errors in the /oracle/admin/insp/bdump/insp_j001_1671296.trc file:
  ORA-12012: error on auto run 49581 work
  ORA-01830: date format picture ends before converting all of the input string
  SAM 7 19:30:11 Mar 2009
  Errors in the /oracle/admin/insp/bdump/insp_j000_1626194.trc file:
  ORA-12012: error on auto work 49580
  ORA-01830: date format picture ends before converting all of the input string
  SAM 7 19:30:11 Mar 2009
  Errors in the /oracle/admin/insp/bdump/insp_j001_1642622.trc file:
  ORA-12012: error on auto run 49581 work
  ORA-01830: date format picture ends before converting all of the input string

  Hello

  Check here Doc ID: 104049.1 and Doc ID: 257909.1, see if they can help out you (first speciallly).

  Concerning

• ORA-27300: OS dependent operating system: CreateThread failed with status: 8

  Hi all

  I'm looking for information on the guide follow error

  ORA-27300: OS dependent operating system: CreateThread failed with status: 8

  ORA-27301: OS Error Message: not enough memory is available to process this command.

  ORA-27302: an error occurred at: ssthrddcr

  Thank you
  Waqas

  Please don't be crazy on me, but in my opinion, this is the wrong place for your question. The fact is that Toshiba doesn't support Windows 2003 server for mobile computing. If you have problems try again with Microsoft.
  As a manufacturer of operating system, they should be able to offer an explanation for each error message. Sorry, but I see no connection between the problems described and Toshiba as a hardware manufacturer.

• ORA-12154 tns could not resolve the specified correct identifier

  I am facing the following problem:

  labVIEW 2012 32 bits 64 bits of Windows 7, 10.2.0.1.0 oracle client (32-bit).

  I created a DSN from Data Sources (ODBC) (32-bit version of what in % windir%\syswow64\odbcad32.exe) pointing to an instance of Oracle 10 g.

  I have test the DSN in this way (IE. Data sources (ODBC) and the connection is successful (which means that the tnsnames.ora is correct).

  I use the "DB tools Open Connection.vi" in order to get connected to this database, passing as parameters the DSN above, the user name and password.

  I get the error:

  ADO error: 0x80040E4D
  Exception occurred in the Microsoft OLE DB provider for ODBC drivers:

  [Oracle] [ODBC] [Ora] ORA-12154: TNS could not resolve the specified correct identifier

  all will help much appreciated

  Thanks in advance

  Hello everyone.

  I already solved the problem (work until late Saturday).

  the solution was to install the latest version of the Oracle customer, namely: Oracle 11 g Release 2 CLIENT for Windows 32 (11.2.0.1.0).

  Now everything works OK.

  I also tested in Windows 7 32 bit (the .vi even and the same Oracle client). This will also OK.

  Thans a lot.

• ORA-12154 for sqlplus username/password@TNS but tns ping works and sqlplus username@TNS works.

  Hello-

  I am facing the following question when I try to connect by using the command prompt sqlplus for Oracle 11.2.0.3 DB installed and running on HP - UX.

  The password is not all special characters & I also tried with the double quotes which did not work.

  Following want to work with username/password@TNSNAME because I'm trying to get my application to connect to the database, the schema mentioned because it uses the jdbc connection with the connection as (username/password@TNS:1521) string.

  C:\Users>sqlplus username/Pa55w0rd@DBNAME;
  
  
  SQL*Plus: Release 11.2.0.1.0 Production on Wed Feb 10 07:21:43 2016
  
  
  Copyright (c) 1982, 2010, Oracle.  All rights reserved.
  
  
  ERROR:
  ORA-12154: TNS:could not resolve the connect identifier specified
  
  
  
  
  Enter user-name:
  C:\Users>tnsping DBNAME
  
  
  TNS Ping Utility for 32-bit Windows: Version 11.2.0.1.0 - Production on 10-FEB-2
  016 07:21:57
  
  
  Copyright (c) 1997, 2010, Oracle.  All rights reserved.
  
  
  Used parameter files:
  C:\app\product\11.2.0\client_2\network\admin\sqlnet.ora
  
  
  
  
  Used TNSNAMES adapter to resolve the alias
  Attempting to contact (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP) (HOST = server.domain) (PORT = 1521)) (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME = DBNAME)))
  OK (50 msec)
  
  
  C:\Users>sqlplus username@DBNAME
  
  
  SQL*Plus: Release 11.2.0.1.0 Production on Wed Feb 10 07:22:05 2016
  
  
  Copyright (c) 1982, 2010, Oracle.  All rights reserved.
  
  
  Enter password:
  
  
  Connected to:
  Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
  With the Partitioning, Automatic Storage Management, OLAP, Data Mining
  and Real Application Testing options
  
  
  SQL> show user
  USER is "username"
  SQL> exit
  Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64
  bit Production
  With the Partitioning, Automatic Storage Management, OLAP, Data Mining
  and Real Application Testing options
  
  
  C:\Users>
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  

  content content of tnsnames.ora & sqlnet.ora:

  DBNAME =
  (DESCRIPTION =
      (ADDRESS = (PROTOCOL = TCP) (HOST = server.domain)  (PORT = 1521))
      (CONNECT_DATA =
          (SERVER = DEDICATED)
          (SERVICE_NAME = DBNAME)
      )
  )
  

  # sqlnet.ora Network Configuration File: C:\app\product\11.2.0\client_2\network\admin\sqlnet.ora
  # Generated by Oracle configuration tools.
  
  
  # This file is actually generated by netca. But if customers choose to 
  # install "Software Only", this file wont exist and without the native 
  # authentication, they will not be able to connect to the database on NT.
  
  
  #SQLNET.AUTHENTICATION_SERVICES= (NTS)
  
  
  NAMES.DIRECTORY_PATH= (TNSNAMES, EZCONNECT)
  
  
  
  
  
  
  
  

  Thanks in advance

  Hello

  sqlplus username/Pa55w0rd@DBNAME;

  Try it without the semicolon;

  sqlplus username/Pa55w0rd@DBNAME

  Regards Thomas