ORA-00972: identifier is too long

Hai all,

SQL > delete / * parallel nologging * / of DWEvent where EVENTTIME < to_date('2012-02-01','YYYY-MM-DD');

ERROR:
ORA-00972: identifier is too long

No idea why?

You have a double quote at the end of your statement.
What happens if you change:

delete /* nologging parallel */ from DWEvent where EVENTTIME < to_date('2012-02-01','YYYY-MM-DD')";
{code}
into:
{code}
delete /* nologging parallel */ from DWEvent where EVENTTIME < to_date('2012-02-01','YYYY-MM-DD');
{code}
?

And by the way: your 'hint' is not really a hint, but only a comment.
Hints start with /*+ YOUR_HINT */, you forgot the + sign.

You can search the syntax easily from http://www.oracle.com/pls/db112/homepage

Tags: Database

Similar Questions

  • * ORA-00972: identifier is too long * when drop index table app

    Hello

    I had some difficulties with dropApplicationTableIndex. He raised an exception ORA-00972:
    java.sql.SQLException: ORA-00972: identifier is too long

    at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:112)
    at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:331)
    at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:288)
    at oracle.jdbc.driver.T4C8Oall.receive(T4C8Oall.java:745)
    at oracle.jdbc.driver.T4CStatement.doOall8(T4CStatement.java:210)
    at oracle.jdbc.driver.T4CStatement.executeForRows(T4CStatement.java:961)
    at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1190)
    at oracle.jdbc.driver.OracleStatement.executeUpdateInternal(OracleStatement.java:1657)
    at oracle.jdbc.driver.OracleStatement.executeUpdate(OracleStatement.java:1626)
    at oracle.spatial.rdf.client.jena.Oracle.executeUpdate(Oracle.java:769)
    at oracle.spatial.rdf.client.jena.GraphOracleSem.dropApplicationTableIndex(GraphOracleSem.java:3695)


    However, the longer name of my models is 23 characters, making it the longest name of characters 27A table (+ _TPL).
    Is there a still shorter limit for the length of model name?

    Thank you

    Kind regards
    Julien

    Hi Julien,

    In fact, the limit for a semantic model, created using the Jena adaptor is 19 characters. This is because the application table index uses TRIPLEIDX as a suffix.

    Best,
    Vlad

  • PL/SQL: ORA-00972: identifier is too long.

    Hi all

    I have a question on the Express request form. I have my form fields that must be completed to save information about the database. It works fine until I click on create a button - I get the following error:
    ORA-06550: line 1, column 243: PL/SQL: ORA-00972: identifier is too long ORA-06550: line 1, column 7: PL/SQL: SQL Statement ignored


Unable to process row of table FIS_REPAT_WITH_APPLICANT_INFO.
    I checked the length of table name, & he is 28 characters long. What could be the problem with this? Any help is appreciated. Thank you in advance.

    Concerning
    Kamo

    Hi Tom,

    Sorry for the late reply. It turns out that my problem was with date formats: I changed the format of the date of my entire application of MON/DD/YY to YYYY-MM-DD, which worked well. However, on a a date field forms I changed the Capture_Date source to to_char (Capture_Date, 'YYYY-MM-DD') that's why I got the error I got.

    At one point, I got an error message: ORA - 06502:PL / SQL: digital or value error: character string buffer too small
    That's why I started another thread: Re: ORA - 06502:PL / SQL: digital or value error: character string buffer too small

  • EXECUTE IMMEDIATE in error &gt; &gt; ORA-00972: identifier is too long

    Hello

    I wrote a code using execute immediate command. This command essentially creates a cursor that selects user_tab_columns table names. These table names are then used inside the statement immediately execute in order to apply the same select statement on the table being selected within the cursor names. The problem is that the above error is thrown saying identifier is too long. I can't understand how to solve this problem.

    Please find the below code:

    Declare
    Cursor C_1 is select distinct table_name
    of user_tab_columns
    where column_name = 'PROGRAM_UPDATE_DATE' AND table_name LIKE '% MISPA '.
    intersect
    Select unique table_name
    of gsi_daily_count;
    table_names varchar2 (100);
    Begin
    C_1 open;
    Loop
    Extract the C_1 in table_names;
    WHEN THE EXIT C_1% NOTFOUND;

    EXECUTE IMMEDIATE "select last_extract_date,
    TO_CHAR (min (largest (nvl (last_update_date, "1 January 10"), nvl (program_update_date, "1 January 10"))), "MON-DD-YY HH24:MI:SS") mi.
    TO_CHAR (max (greatest (nvl (last_update_date, "1 January 10"), nvl (program_update_date, "1 January 10"))), "MON-DD-YY HH24:MI:SS") my
    of ' | table_names |
    "Last_extract_date group".
    order of last_extract_date desc;';

    End loop;
    Close C_1;
    COMMIT;
    End;
    /


    Help, please.

    Kind regards
    Hossam 
    declare
  cursor C_1
  is
  select distinct table_name
    from user_tab_columns
   where column_name = 'PROGRAM_UPDATE_DATE'
     and table_name LIKE 'MISPA%'
  intersect
  select unique table_name
    from gsi_daily_count;

  table_names varchar2(100);
begin
  open C_1;
  loop
    fetch C_1 into table_names;
    exit when c_1%notfound;

    execute immediate
      'select last_extract_date,
              to_char(min(greatest(nvl(last_update_date,''01-Jan-10''),nvl(program_update_date,''01-Jan-10''))),''DD-MON-YY HH24:MI:SS'') mi,
              to_char(max(greatest(nvl(last_update_date,''01-Jan-10''),nvl(program_update_date,''01-Jan-10''))),''DD-MON-YY HH24:MI:SS'') ma
         from'|| table_names ||
      'group by last_extract_date
        order by last_extract_date desc;';
  end Loop;
  close C_1;
  commit;
End;

    Here is the list of question I see in this code.

    1. in the SQL string, you must have a after the keyword and before the GROUP BY keyword.

    2. you should not use ';' in EXECUTE IMMEDIATE. You must remove it.

    3. the result set returned by the EXECUTE IMMEDIATE should be stored in a Variable. You use the INTO LEDGES INTO clause or in BULK to this effect.

  • 11g ODI identifier is too long on source ORACLE

    Hello

    I just migrated to ODI 10 ODI 11 g g but it seems that one of my script doesn't work. Whenever I run, I have the following error message:

    ODI-1227: SS_0 (load) task fails on the source of connection ORACLE POM

    Caused by: java.sql.SQLSyntaxErrorException: ORA-00972: identifier is too long

    After some research it seems that on ODI 11 g, the identifier must be a maximum of 30 characters in the alias column, so my problem is the following application

    Select*
    END
    NVL(ENCADRANT_INTERVENANT.SI_APTITUDE_TRAJET_LONG,0)C15_ENC_SI_APTITUDE_LONG_TRAJET
    OfPROD_DSN.
    where(1 = 1)

    So I went (physical) topology, change the field 'Maximum length of name of column' 25 on Advanced tab but it does not work.


    Any idea, please?


    Kind regards

    Jean

    There is limitation aka oracle. See the Oracle SQL language reference.

    Module IKM look the parameter 'Maximum length of ColumnName', this setting works for tear. So if you're boning now, ODI truncates all the columns including more then 25 characters.

    You can solve the problem:

    (1) module knowledge of change in the production of alias

    (2) create view your alias small columns table PROD_DSN

  • identifier is too long

    Hello
    I run the script but I got problem below. How will I know which column is the reason for the problem?

    ERROR on line 1:
    ORA-00972: identifier is too long

    Hello

    Human Chen wrote:
    no column above is really with over 30 char

    Really?
    Format your code to make it easier to identify:

    insert into tw.EDI_PARTNER_MESSAGE
(     edi_partner_code
,     edi_event_code
...
,     outbound_file_location
,     dest_email_addr
--              1         2         3         4
--     1234567890123456789012345678901234567890
,     edi_bk_directflow_indedi_partner_code
,     edi_event_code
,     edi_message_code ...

    A comma is missing.

  • identifier is too long, when you create a view

    Hi all
    When I am trying to run the initial load using OBI apps 7.9.5.2 SCCM with I get the following error for the SDE mappings...
                72 : 42000 : java.sql.SQLException: ORA-00972: identifier is too long

java.sql.SQLException: ORA-00972: identifier is too long


     at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:125)

     at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:316)

     at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:282)

     at oracle.jdbc.driver.T4C8Oall.receive(T4C8Oall.java:639)

     at oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:185)

     at oracle.jdbc.driver.T4CPreparedStatement.execute_for_rows(T4CPreparedStatement.java:633)

     at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1086)

     at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:2984)

     at oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(OraclePreparedStatement.java:3057)

     at com.sunopsis.sql.SnpsQuery.executeUpdate(SnpsQuery.java)

     at com.sunopsis.dwg.dbobj.SnpSessTaskSql.execSrcOrders(SnpSessTaskSql.java)

     at com.sunopsis.dwg.dbobj.SnpSessTaskSql.treatTaskTrt(SnpSessTaskSql.java)

     at com.sunopsis.dwg.dbobj.SnpSessTaskSqlC.treatTaskTrt(SnpSessTaskSqlC.java)

     at com.sunopsis.dwg.dbobj.SnpSessTaskSql.treatTask(SnpSessTaskSql.java)

     at com.sunopsis.dwg.dbobj.SnpSessStep.treatSessStep(SnpSessStep.java)

     at com.sunopsis.dwg.dbobj.SnpSession.treatSession(SnpSession.java)

     at com.sunopsis.dwg.cmd.DwgCommandSession.treatCommand(DwgCommandSession.java)

     at com.sunopsis.dwg.cmd.DwgCommandBase.execute(DwgCommandBase.java)

     at com.sunopsis.dwg.cmd.e.i(e.java)

     at com.sunopsis.dwg.cmd.g.y(g.java)

     at com.sunopsis.dwg.cmd.e.run(e.java)

     at java.lang.Thread.run(Unknown Source)  
    This is my sql code in the description tab

      
create or replace view APPS.C$_0W_ORA_INT_ORG_D
(
     C1_ORGANIZATION_ID,
     C2_ORGANIZATION_CODE,
     C3_ORGANIZATION_NAME,
     C4_BUSINESS_GROUP_ID,
     C5_BUSINESS_GROUP_NAME,
     C6_SET_OF_BOOKS_ID,
     C7_OPERATING_UNIT,
     C8_OPERATING_UNIT_NAME,
     C9_LEGAL_ENTITY,
     C10_LEGAL_ENTITY_NAME
)
as select     
     
     TO_CHAR(SQ_ORG_ORGANIZATION_DEFINITION.ORGANIZATION_ID)        C1_ORGANIZATION_ID,
     SQ_ORG_ORGANIZATION_DEFINITION.ORGANIZATION_CODE        C2_ORGANIZATION_CODE,
     SQ_ORG_ORGANIZATION_DEFINITION.ORGANIZATION_NAME        C3_ORGANIZATION_NAME,
     TO_CHAR(SQ_ORG_ORGANIZATION_DEFINITION.BUSINESS_GROUP_ID)        C4_BUSINESS_GROUP_ID,
     SQ_ORG_ORGANIZATION_DEFINITION.BUSINESS_GROUP_NAME        C5_BUSINESS_GROUP_NAME,
     TO_CHAR(SQ_ORG_ORGANIZATION_DEFINITION.SET_OF_BOOKS_ID)        C6_SET_OF_BOOKS_ID,
     TO_CHAR(SQ_ORG_ORGANIZATION_DEFINITION.OPERATING_UNIT)        C7_OPERATING_UNIT,
     SQ_ORG_ORGANIZATION_DEFINITION.OPERATING_UNIT_NAME        C8_OPERATING_UNIT_NAME,
     TO_CHAR(SQ_ORG_ORGANIZATION_DEFINITION.LEGAL_ENTITY)        C9_LEGAL_ENTITY,
     SQ_ORG_ORGANIZATION_DEFINITION.LEGAL_ENTITY_NAME        C10_LEGAL_ENTITY_NAME
from     APPS.ODI_SQ_ORG_ORGANIZATION_DEFINITION   SQ_ORG_ORGANIZATION_DEFINITION
where     (1=1)
    Any suggestions? Please help me

    Thank you
    saichand.v

    Hello

    Try changing the "maximum Table name length' and '"column name maximum length"in Manager topology ODI.» This is, in the "other" tab of the chosen technology.

    Set the new value = original value - 5

    You must assign the appropriate value to 'column name maximum length ".
    setting for staging technology.

    Thank you
    Fati

  • identifier is too long: expdp filtering using QUERY off TABLES =.

    All,

    I run large expdp work using a .bat file.  An example of one of the lines is the following:

    expdp directory "" / as sysdba "" = IMPORT_DB dumpfile=vismag_brightness%%U.dmp logfile = vismag_brightness.log ALL TABLES = sat_cat_owner.vismag_brightness QUERY = sat_cat_owner.vismag_brightness = compression:'------"where exists (" select visual_magnitude_uuid in the sat_cat_owner.visual_magnitude where sat_cat_owner.visual_magnitude.visual_magnitude_uuid=sat_cat_owner.vismag_brightness.visual_magnitude_uuid)\ "')"

    Present the results of .bat to this:

    OracleExportDataPumpIssues.png

    I then tried to put it in a settings file.  As always, you can see in the picture above, he already gave me an error, but I corrected which and he always gave me the same error.  The application was the same as above, only had no slashes return of evasion.

    Now this is why I am sure that I am right escape.  Now, I just need to find the reason for the identifier is too long.

    Here's a picture showing other odd behavior, trying to simplify the query to see if its because the query is too long.  AND if it is because its too long..how for I can config so it can handle?

    OracleSimpler.png

    The difference in the image above, is that the first test has only \"...while the second is what worked for me before top (if I try without the single quotes, it fails on citing the issue for the important query).  So the second cmd, as I have said, has "\" instead of just \"...and it does not work!"  When he did above for the larger request, but it gives error separated.

    Help, please!  Thank you

    Hello

    Try this instead

    Query ='sat_cat_owner.vismag_brightness: "Where exists (select visual_magnitude_uuid from the sat_cat_owner.visual_magnitude where sat_cat_owner.visual_magnitude.visual_magnitude_uuid = ku$ .visual_magnitude_uuid)" "

    Ku$ is an alias of special for the object currently being extraction - I think that in case you want to use exists, you must use this syntax - give it a try and see what happens.

    Other than that can replace you an IN clause instead?

    See you soon,.

    Rich

  • SQL error: ORA-00910: specified length too long for its data type

    Using Oracle 11.2.0.1 on Oracle Linux 5.8 x 64

    I try to install Zabbix http://www.zabbix.com and uses the Oracle database as the data store. The script of the diagram provided below does not work.
    CREATE TABLE maintenances (
     maintenanceid            number(20)                                NOT NULL,
     name                     nvarchar2(128)  DEFAULT ''                ,
     maintenance_type         number(10)      DEFAULT '0'               NOT NULL,
     description              nvarchar2(2048) DEFAULT ''                ,
     active_since             number(10)      DEFAULT '0'               NOT NULL,
     active_till              number(10)      DEFAULT '0'               NOT NULL,
     PRIMARY KEY (maintenanceid)
);
    When I run it, I get
    Error at Command Line:5 Column:42
Error report:
SQL Error: ORA-00910: specified length too long for its datatype
00910. 00000 -  "specified length too long for its datatype"
*Cause:    for datatypes CHAR and RAW, the length specified was > 2000;
           otherwise, the length specified was > 4000.
*Action:   use a shorter length or switch to a datatype permitting a
           longer length such as a VARCHAR2, LONG CHAR, or LONG RAW
    According to the oracle documentation for nvarchar2 limit is 4000. What am I missing here?

    "4000 bytes is the ultimate maximum." You can say 4000 * characters *, but it will always be limited to 4000 * bytes *. "
    http://asktom.Oracle.com/pls/Apex/f?p=100:11:0:P11_QUESTION_ID:1224836384599 #201073000346459201\

    "The maximum length of the column is determined by the definition of national character set. The width of the character NVARCHAR2 data specifications match the number of characters. The authorized maximum column size is 4000 bytes. »
    http://docs.Oracle.com/CD/E11882_01/server.112/e26088/sql_elements001.htm#SQLRF50976

    Furthermore, you treat numbers as STRINGS, remove the quotes around your zero.

  • identifier too long on heterogeneous services-&gt; MSSQL

    Got a strange problem, a little
    We got the heterogeneous services, pointing to a MSSQL Server.

    When I run

    Select * from table_name32charslong@mssql_server

    I get: SQL error: ORA-00972: identifier is too long

    Logic because the name of the table msserver is over 30 characters.

    Can it be solved without renaming the table / side view msserver?

    Thank you


    4Eyes

    BluShadow wrote:
    HS can only deal in restraint of Oracle specifications. i.e. table names must be is no longer than 30 characters that oracle would expect of his own paintings.

    I came across the same problem myself with a HS connection to an Excel spreadsheet that allows 32 chrs for worksheet names.

    Looks like you will need to rename the table, either create a view against it. ;)

    Well, OP has not to rename the table or create a view against it on the side MSSQL. He or she can use DBMS_HS_PASSTHROUGH:

    SQL> SELECT * FROM LONGER_THAN_THIRTY_CHARACTERS_TABLE_NAME@MDB
  2  /
SELECT * FROM LONGER_THAN_THIRTY_CHARACTERS_TABLE_NAME@MDB
              *
ERROR at line 1:
ORA-00972: identifier is too long

SQL> SET SERVEROUTPUT ON
SQL> DECLARE
  2          c  INTEGER;
  3          nr INTEGER;
  4          id NUMBER;
  5          a  VARCHAR2(10);
  6      BEGIN
  7          c := DBMS_HS_PASSTHROUGH.OPEN_CURSOR@MDB;
  8          DBMS_HS_PASSTHROUGH.PARSE@MDB(c,'SELECT * FROM LONGER_THAN_THIRTY_CHARACTERS_TABLE_NAME');
  9          LOOP
 10            nr := DBMS_HS_PASSTHROUGH.FETCH_ROW@MDB(c);
 11            EXIT WHEN nr = 0;
 12            DBMS_HS_PASSTHROUGH.GET_VALUE@MDB(c,1,id);
 13            DBMS_HS_PASSTHROUGH.GET_VALUE@MDB(c,2,a);
 14            DBMS_OUTPUT.PUT_LINE('ID = ' || id || ' A = ' || a);
 15          END LOOP;
 16          DBMS_HS_PASSTHROUGH.CLOSE_CURSOR@MDB(c);
 17  END;
 18  /
ID = 1 A = test

PL/SQL procedure successfully completed.

SQL>

    If OP wants to query the SQL table:

    SQL> CREATE OR REPLACE
  2    TYPE LONG_TBL_NAME_OBJ_TYPE
  3      AS OBJECT(
  4                ID NUMBER,
  5                A  VARCHAR2(50)
  6               )
  7  / 

Type created.

SQL> CREATE OR REPLACE
  2    TYPE LONG_TBL_NAME_TBL_TYPE
  3      AS TABLE OF LONG_TBL_NAME_OBJ_TYPE
  4  / 

Type created.

SQL> CREATE OR REPLACE
  2    FUNCTION get_data_from_link
  3      RETURN LONG_TBL_NAME_TBL_TYPE
  4      PIPELINED
  5      IS
  6          c                 INTEGER;
  7          nr                INTEGER;
  8          long_tbl_name_obj LONG_TBL_NAME_OBJ_TYPE := LONG_TBL_NAME_OBJ_TYPE(NULL,NULL);
  9      BEGIN
 10          c := DBMS_HS_PASSTHROUGH.OPEN_CURSOR@MDB;
 11          DBMS_HS_PASSTHROUGH.PARSE@MDB(c,'SELECT * FROM LONGER_THAN_THIRTY_CHARACTERS_TABLE_NAME');
 12          LOOP
 13            nr := DBMS_HS_PASSTHROUGH.FETCH_ROW@MDB(c);
 14            EXIT WHEN nr = 0;
 15            DBMS_HS_PASSTHROUGH.GET_VALUE@MDB(c,1,long_tbl_name_obj.id);
 16            DBMS_HS_PASSTHROUGH.GET_VALUE@MDB(c,2,long_tbl_name_obj.a);
 17            PIPE ROW(long_tbl_name_obj);
 18          END LOOP;
 19          DBMS_HS_PASSTHROUGH.CLOSE_CURSOR@MDB(c);
 20          RETURN;
 21  END;
 22  / 

Function created.

SQL> SELECT  *
  2    FROM  TABLE(get_data_from_link)
  3  / 

        ID A
---------- --------------------------------------------------
         1 test

SQL>

    SY.

  • IMPDP SQLFILE: constraint_name multibyte characters leads to ORA-00972

    Hello

    I'm actually constraint_name made of multibyte characters (for example: constrain_name = "VALIDA_CONFIRMAÇÃO_PREÇO13").
    Of course this Bad Idea® is hereditary (I'm against all the stuff of fantasy as water in the names of files or directories on my filesystem...)

    The scenario is as follows:
    0 - I'm supposed to do a 'remap_schema '. Everything in the schema SCOTT should now be in a schema NEW_SCOTT.
    1 - the scott schema is exported via datapump
    2 - I'm an impdp with SQLFILE to remove all the DDL (table, packages, synonyms, etc...)
    3. I do a few sed on the sqlfile generated to replace each occurrence of SCOTT at NEW_SCOTT (this part is OK)
    4. once the modified sqlfile is executed, I'm doing an impdp with DATA_ONLY.

    (The scenario was envisioned in this thread: {message identifier: = 10628419})

    I get a few ORA-00972: identifier is too long to step 4, when you run the sqlfile.
    I see that some DDL for creating the constraint in the file (generated in step # 2) is read as follows:
    ALTER TABLE "TW_PRI"."B_TRANSC" ADD CONSTRAINT "VALIDA_CONFIRMAÃÃO_PREÃO14" CHECK ...
    Of course, the original name of the constraint with the cedilla and the tilde translates to something that is longer than 30 char/byte...

    As the original name is the Brazil, I also tried to add an EXPORT LANG = pt_BR. UTF-8 in my script before you run the impdp for sqlfile. It doesn't change anything. (the original $LANG is en_US. UTF-8)

    To create a unit test for this thread, I tried to reproduce it on my sandbox database... but, I don't have the issue. :-(

    The real system is a database of 4-nodes on Exadata (11.2.0.3) with NLS_CHARACTERSET = AL32UTF8.
    My sandbox database is a 11.2.0.1 (nonRAC) on RHEL4 AL32UTF8 also.

    The constraint_name argument is the same on the two system: I checked byte by byte using DUMP() on the constraint_name argument.

    Feel free to make light and/or seek clarification if necessary.


    Thanks in advance for those who will take their time to read all this.
    :-)

    --------
    I decided to register my testcase to my sandbox database, even if it does NOT reproduce the issue + (maybe I'm missing something obvious...) +.

    I use the following files.
    -createTable.sql:
    $ cat createTable.sql 
drop table test purge;

create table test
(id integer,
val varchar2(30));

alter table test add constraint VALIDA_CONFIRMAÇÃO_PREÇO13 check (id<=10000000000);

select constraint_name, lengthb(constraint_name) lb, lengthc(constraint_name) lc, dump(constraint_name) dmp
from user_constraints where table_name='TEST';
    -expdpTest.sh:
    $ cat expdpTest.sh 
expdp scott/tiger directory=scottdir dumpfile=testNonAscii.dmp tables=test
    -impdpTest.sh:
    $ cat impdpTest.sh 
impdp scott/tiger directory=scottdir dumpfile=testNonAscii.dmp sqlfile=scottdir:test.sqlfile.sql tables=test
    It comes to the race:
    [oracle@Nicosa-oel test_nonAsciiColName]$ sqlplus scott/tiger

SQL*Plus: Release 11.2.0.1.0 Production on Tue Feb 12 18:58:27 2013

Copyright (c) 1982, 2009, Oracle.  All rights reserved.


Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options

SQL> @createTable

Table dropped.


Table created.


Table altered.


CONSTRAINT_NAME                  LB       LC
------------------------------ ---------- ----------
DMP
--------------------------------------------------------------------------------
VALIDA_CONFIRMAÇÃO_PREÇO13             29         26
Typ=1 Len=29: 86,65,76,73,68,65,95,67,79,78,70,73,82,77,65,195,135,195,131,79,95
,80,82,69,195,135,79,49,51


SQL> exit
Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
[oracle@Nicosa-oel test_nonAsciiColName]$ ./expdpTest.sh 

Export: Release 11.2.0.1.0 - Production on Tue Feb 12 19:00:12 2013

Copyright (c) 1982, 2009, Oracle and/or its affiliates.  All rights reserved.

Connected to: Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
Starting "SCOTT"."SYS_EXPORT_TABLE_01":  scott/******** directory=scottdir dumpfile=testNonAscii.dmp tables=test 
Estimate in progress using BLOCKS method...
Processing object type TABLE_EXPORT/TABLE/TABLE_DATA
Total estimation using BLOCKS method: 0 KB
Processing object type TABLE_EXPORT/TABLE/TABLE
Processing object type TABLE_EXPORT/TABLE/CONSTRAINT/CONSTRAINT
. . exported "SCOTT"."TEST"                                  0 KB       0 rows
Master table "SCOTT"."SYS_EXPORT_TABLE_01" successfully loaded/unloaded
******************************************************************************
Dump file set for SCOTT.SYS_EXPORT_TABLE_01 is:
  /home/oracle/scott_dir/testNonAscii.dmp
Job "SCOTT"."SYS_EXPORT_TABLE_01" successfully completed at 19:00:22

[oracle@Nicosa-oel test_nonAsciiColName]$ ./impdpTest.sh 

Import: Release 11.2.0.1.0 - Production on Tue Feb 12 19:00:26 2013

Copyright (c) 1982, 2009, Oracle and/or its affiliates.  All rights reserved.

Connected to: Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
Master table "SCOTT"."SYS_SQL_FILE_TABLE_01" successfully loaded/unloaded
Starting "SCOTT"."SYS_SQL_FILE_TABLE_01":  scott/******** directory=scottdir dumpfile=testNonAscii.dmp sqlfile=scottdir:test.sqlfile.sql tables=test 
Processing object type TABLE_EXPORT/TABLE/TABLE
Processing object type TABLE_EXPORT/TABLE/CONSTRAINT/CONSTRAINT
Job "SCOTT"."SYS_SQL_FILE_TABLE_01" successfully completed at 19:00:32

[oracle@Nicosa-oel test_nonAsciiColName]$ cat scott_dir/test.sqlfile.sql 
-- CONNECT SCOTT
ALTER SESSION SET EVENTS '10150 TRACE NAME CONTEXT FOREVER, LEVEL 1';
ALTER SESSION SET EVENTS '10904 TRACE NAME CONTEXT FOREVER, LEVEL 1';
ALTER SESSION SET EVENTS '25475 TRACE NAME CONTEXT FOREVER, LEVEL 1';
ALTER SESSION SET EVENTS '10407 TRACE NAME CONTEXT FOREVER, LEVEL 1';
ALTER SESSION SET EVENTS '10851 TRACE NAME CONTEXT FOREVER, LEVEL 1';
ALTER SESSION SET EVENTS '22830 TRACE NAME CONTEXT FOREVER, LEVEL 192 ';
-- new object type path: TABLE_EXPORT/TABLE/TABLE
CREATE TABLE "SCOTT"."TEST" 
   (     "ID" NUMBER(*,0), 
     "VAL" VARCHAR2(30 BYTE)
   ) SEGMENT CREATION DEFERRED 
  PCTFREE 10 PCTUSED 40 INITRANS 1 MAXTRANS 255 COMPRESS FOR OLTP LOGGING
  TABLESPACE "MYTBSCOMP" ;
 
-- new object type path: TABLE_EXPORT/TABLE/CONSTRAINT/CONSTRAINT
ALTER TABLE "SCOTT"."TEST" ADD CONSTRAINT "VALIDA_CONFIRMAÇÃO_PREÇO13" CHECK (id<=10000000000) ENABLE;
    I was expecting the cedilla and the tilde characters not displayed correctly...

    Published by: Nicosa on February 12, 2013 19:13

    Hello
    I had some strange effects if I didn't set the translation be utf8 in my ssh client (PuTTY in my case). Is - this somehow something that automatically happens in an environment, but not the other?

    In putty, this is the window-> translation and then choose utf8

    Also make sure that's not sed plague rather than impdp?

    See you soon,.
    Harry

  • ORA-00972 dynamic sql error

    Here is my code... I got THE FOLLOWING ERROR message

    "ORA-00972: identifier is too long.
    ORA-06512: at "VVMS_BATCH. QUEUE_DYNAMIC', line 26
    ORA-06512: at line 2'

    Code:

    create or replace
    procedure sales_dynamic is
    cursor cur_sales is
    Select sales_CATEGORY_ID, sales_ITEM_STATUS, sales_ITEM_KEY, sales_ID from sales_ITEM_HISTORY where sales_ITEM_STATUS = 'OH' and ONHOLD_DT < sysdate;
    / * number of v_err_code;
    v_err_msg varchar2 (64); * /

    type v_source_table is table of the sales_category.source_table%type;
    z_v_source_table v_source_table: = v_source_table();
    long stmt (2000);
    v_ot varchar2 (2);

    Start
    I'm looping cur_sales
    Start
    v_ot: = 'OT ';
    Select to bulk source_table fired into z_v_source_table from ventes_categorie where sales_CATEGORY_ID = i.sales_CATEGORY_ID;

    j in z_v_source_table.first... loop z_v_source_table. Last

    stmt: = 'start' |' update '. z_v_source_table (j) | q '(set sales_ITEM_STATUS = ('OT") where sales_ITEM_KEY = i.sales_ITEM_KEY)';
    immediately execute stmt USING z_v_source_table (j), i.sales_ITEM_KEY;
    dbms_output.put_line ('run' | z_v_source_table (j));
    end loop;
    end;
    end loop;
    end sales_dynamic; 
    executing update lois ( set table_id = ('OT') where table_id = i.ey_id)
                                       ^    ^
                                       |    |
                                       |    |
                                       remove this parenthesis

    your stmt variable should resemble:

    stmt :='update '|| z_v_source_table(j) ||' set sales_ITEM_STATUS = ''OT'' where sales_ITEM_KEY = i.sales_ITEM_KEY';

  • Column name is too long

    When loading the data from the XML source I get following error
    ORA-00972: identifier is too long
    I understand that some are the name of the column over source of dansMon then 30 tank (limit of Oracle) but I would like to know what it
    to be changed in the revenge to choose only thirty first characters of the name of the column if the column name is Char, then 30.
    Works LKM fine as she take only the first 30 tank to create the name of the table, I think that it take this crib of the topology setting.
    But what have to change in revenge to take only the first 30 tank for the column name.
    I'm creating table target on the fly and I don't want to change the name of each column in the target table, it's going to be a lot of work for me.
    Please let me know your opinion on this.

    Thank you

    I have prepared the KM for you because we had to change some steps... send me an email and I will answer it with the attached IKM.

    You can get my email on my profile...

  • Shuttle value too long for use in LOV sql cascading

    Hello

    On APEX 4.2.2.0.11 & Oracle 10.2.0.5.0:

    I have a shuttle service set up as well as a select list with of LOV cascading.

    The shuttle shows organization name and returns a list of the IDs of the colon separated.

    The selection list shows the so-called events belonging to the organizations selected in the shuttle.

    The selection list is implemented as LOV cascading with the shuttle as a parent element.

    This works fine as long as the length of the shuttle point value does not exceed 4000 characters.

    If so, the LOV - sql select list will give an ' ORA-01704: string literal too long "-error on the instr function ().

    This is the query:

    Select distinct TST. NAAM as display_value, TST.ID as return_value

    of the OTE ORGS

    Join the LIFO ADG ON (ADG. OTE_ID = OTE.ID)

    Join the DNR PART on (DNR. ADG_ID = ADG.ID)

    Join the TDR ON REGRET (TDR. DNR_ID = DNR.ID)

    Join the TEST TCT ON (TST.ID = RDT. TST_ID)

    where instr (': ' |: P1_ORG |) ':', ':' || OTE.ID | ') > 0

    order by 1

    Does anyone know how to make reference to the shuttle-value in sql, even if it is longer than 4000 characters?

    Well, I found a way to use LOVs cascading on page elements with values exceeding 4000 characters:

    Let's say I have a shuttle named P1_ORGANISATIE with "List of values" box, a dynamic LOV named "Source: lists of values Query" containing the value:

    Select NAAM as display_value, ID like return_value

    of NINEHAM

    order by 1

    If the number of records-NINEHAM is insufficient, the length of the value of P1_ORGANISATIE, which is a list of concatenated with colon separated digital ID, can exceed 4000 characters.

    Now suppose I have a list of selection called P1_TEST that is connected through "List of values"-> "En cascade LOV Parent article (s)" with P1_ORGANISATIE using a named LOV dynamics with "Source: lists of values Query" containing:

    Select distinct TST. NAAM as display_value, TST.ID as return_value

    of the OTE NINEHAM

    Join the AFDELINGEN ADG ON (ADG. OTE_ID = OTE.ID)

    Join the DEELNEMERS DNR ON (DNR. ADG_ID = ADG.ID)

    Join TESTDEELNEMERS TDR WE (TDR. DNR_ID = DNR.ID)

    Join TESTEN TST ON (TST.ID = RDT. TST_ID)

    where instr (":" |: P1_ORGANISATIE |) '':'', '':'' || OTE.ID | '':'') > 0

    order by 1

    In this case, when P1_ORGANISATIE exceeds 3998 characters, you'll get an "ORA-01704: string literal too long"-error and the P1_TEST will show an element called "undefined".

    A way around this is possible because for a named LOV, you can use a "function that returns a sql query" instead of a simple sql query. In other words, we can apply in the context of PL/SQL and thus have maximum for expressions of 32767 instead of 4000 characters. In addition, it is possible to use the two APEX_UTIL. STRING_TO_TABLE and APEX_COLLECTION.

    Setting "Source: lists of query values" on the LOV appointed to P1_TEST with the following code will work:

    DECLARE

    l_selected APEX_APPLICATION_GLOBAL. VC_ARR2;

    l_qry varchar2 (32767): =.

    "Select distinct TST. NAAM as display_value, TST.ID as return_value

    of the OTE NINEHAM

    Join the AFDELINGEN ADG ON (ADG. OTE_ID = OTE.ID)

    Join the DEELNEMERS DNR ON (DNR. ADG_ID = ADG.ID)

    Join TESTDEELNEMERS TDR WE (TDR. DNR_ID = DNR.ID)

    Join TESTEN TST ON (TST.ID = RDT. TST_ID)

    $1

    order by 1';

    BEGIN

    IF: P1_ORGANISATIE IS NULL

    OR LENGTH(:P1_ORGANISATIE)<=>

    THEN RETURN

    Replace (l_qry

    ,'$1'

    ,' where instr (":" |: P1_ORGANISATIE |) '':'', '':'' || OTE.ID | '':'') > 0'

    );

    ON THE OTHER

    l_selected: = APEX_UTIL. STRING_TO_TABLE(:P1_ORGANISATIE);

    APEX_COLLECTION. CREATE_OR_TRUNCATE_COLLECTION (p_collection_name-online 'ORGANISATIE_COLLECTIE');

    FOR id IN 1.l_selected.count

    LOOP

    APEX_COLLECTION.add_member (p_collection_name-online 'ORGANISATIE_COLLECTIE'

    p_n001-online to_number (l_selected (id))

    );

    END LOOP;

    RETURN

    Replace (l_qry

    ,'$1'

    ,'join apex_collections ON APC (APC. COLLECTION_NAME = "ORGANISATIE_COLLECTIE" AND APC. N001 = OTE.ID)"

    );

    END IF;

    END;

  • Literal string is too long and too small string buffer

    Hello

    Can someone please explain what the difference is between these two errors.

    The maximum size of the character in SQL is 4000 and PL/SQL its 32 k. So if a string literal exceeds this limit "string literal too long" error message is triggered by oracle.

    Here is an example

    SQL> select 'xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
  2  xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
  3  xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
  4  xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
  5  xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
  6  xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
  7  xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
  8  xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
  9  xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
 10  xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
 11  xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
 12  xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
 13  xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
 14  xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
 15  xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
 16  xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
 17  xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
 18  xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
 19  xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
 20  xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
 21  xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
 22  xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
 23  xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
 24  xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
 25  xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
 26  xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
 27  xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
 28  xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
 29  xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
 30  xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
 31  xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx' str
 32    from dual;
select 'xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
       *
ERROR at line 1:
ORA-01704: string literal too long

    Now, when you try to set a string variable with a value greater than the defined size, you get "too small character string buffer.

    Here is an example

    SQL> declare
  2    var varchar2(1);
  3  begin
  4    var := 'aa';
  5  end;
  6  /
declare
*
ERROR at line 1:
ORA-06502: PL/SQL: numeric or value error: character string buffer too small
ORA-06512: at line 4

    Oracle error message there two of each, one for SQL and one for PL/SQL.

    ORA-19011: character string buffer too small

    Cause : the result of the chain asked is too big to go back

    Action : get the result like a lob instead

    ORA-01704: string literal too long

    Cause : the string literal is longer than 4000 characters.

    Action : use a string literal of more than 4,000 characters. Longer values can only be entered using bind variables.

    PLS-01905: character string buffer too small

    Cause : an error occurred while moving a string from a source to a destination. This error occurs if, for example, an attempt is made to move an a string of 10 characters into a buffer of 1 character. The cause of this error may not always be obvious. For example, the following will cause this error: a varchar2 (1); b the number; b: = 10; a: = b; An error occurs because an implicit conversion causes the number 10 to become the string '10', which does not fit in memory buffer of characters of 1 assigned to the variable.

    Action : first, look for the character string assignment statements where the size of the buffer is incompatible. If there is none found, then consider the case of an implicit conversion shown in the example above.

    PLS-00172: string literal too long

    Cause : the string literal is longer than 32767octets.

    Action : use a string literal of at most 32767octets.

Maybe you are looking for

  • Watch is not sync old calendarposts

    I just took my watch and I love it, but there is a problem with the calendar synchronization. On the phone to my work, I have a Google Calendar and an Exchange calendar for work, but they do not synchronize right. The only things Google Calendar sync

  • The cutting tool are not sent Snip to the e-mail recipient.

    The cutting tool are not sent Snip of recipient of mail on Windows Live Mail 2011.  Had worked on earlier versions.  Click on the send Snip button, and nothing happens.

  • Dv4-1131tx keeps in hibernation

    Hi, I am facing a problem every time I do something that is heavy, that is to say that consumes more resources cpu for most playing a laptop of the game.the is inclined to go in hibernation at random several times and the left side of the laptop also

  • Family Safety: could not connect to the site Web Family Safety - "try again later".

    I am connected to MSLive with my account, the same one that I am connected to help with this issue.  I also see my mailbox outlook.com, so that my account is active and works very well. When I go to familysafety.microsoft.com, the URL bar changes sev

  • Cisco IOS it helps 3rd party certificate

    Hello Can I use a 3rd party such as verisign, on Cisco IOS CA? All I can see on cisco.com is a self-signed certificate to the router. Thank you -santo-