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

Similar Questions

• EXECUTE IMMEDIATE in error > > 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.

• * 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

• 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

• 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
  Of	PROD_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

• 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                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        
  

• 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.

• 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

• String control GPIB, too long when you use a multicore processor machine

  I have a HP 3457 A multimeter I communicate with the help of GPIB. I have two machines that have identical operating systems installed. CentOS 4.8 (equivalent to Red Hat Enterprise Linux 4.8) with the version of the kernel: 2.6.9 - 89.0.25.ELsmp.

  The first machine has a Pentium 2.8 GHz processor. We used this setup for a few years now without any problems. Given that the core processors go far, we need get our system working on a multi-core computer software. So, I loaded all our software on a new machine with an Intel Core 2 Duo processor. I have only this one all deadlines irregular left before calling this experience.

  In our code, we issue the following command to the multimeter and check a response:

  char * pm_init = "QR 0; PRESET; BACK OF THE TERM; END; LOCK ON; SREAL OFORMAT; « ;

  If (!) () (er = ibwrt (pm_ud, pm_init, strlen (pm_init))) & ERR))

  On the Pentium machine, it works fine. The multimeter does not have on the Core2 Duo computer. If I have this divide into two commands as follows:

  ER = ibwrt (pm_ud, "QR 0;") PRESET; BACK of the TERM; ", strlen (" QR 0; ") PRESET; TERM BACK ;")) & ERR

  If (!) () (er = ibwrt (pm_ud, "END; LOCK ON; OFORMAT SREAL. ", strlen ("END; LOCKING IN ONTARIO; OFORMAT SREAL ;"))) "& ERR))

  It works on both machines. However, it is a ugly real difficulty. Can someone tell me what is so different from the way in which the driver NOR past the verses of the long chain the two shorter chains?

  Thank you.

  Sorry, I thought that VISA facility would bring along the difficulty that we need, but when I look back it did not include a fix for Linux.

  This means that we don't currently have a driver available that will solve this problem, but there is a solution, if this is indeed the problem you see.

  The workaround is to disable DMA for your GPIB interface. To do this, you will need to open a handle to the jury and use the ibdma command to disable DMA. For example:

  handle = ibfind ("GPIB0");

  ibdma (handle, 0);

  At this point you should probably keep the handle open until your program is out, to ensure nothing resets the jury and allows again to DMA.

  As you can imagine, disable DMA can have an impact on performance in your application. If you make small, such transfers would probably be with a multimeter, you are unlikely to notice a difference in performance. If you transfer large size pads, you may encounter CPU utilization and more low than you would when using DMA.

  Please let me know if this workaround lets your program works, because this will tell us if this is the problem you are having, or if something goes wrong.

  -Jason S.

• Name of the item too long when you use ROWTYPE

  I encountered a problem with the xml elements names longer than 30 characters. Seems that it has something to do with ROWTYPE. Creation of this function is successful:
  
  < pre >
  FUNCTION to CREATE or REPLACE test_fnc
  RETURN OF XMLTYPE
  AS
  var_return XMLTYPE.
  l_dummy DUAL.dummy%TYPE;
  BEGIN
  SELECT dummy INTO l_dummy FROM DUAL;
  
  SELECT XMLCONCAT (XMLELEMENT)
  "TEST."
  XMLFOREST)
  l_dummy "THIS_IS_OVER_30_CHARACTERS_LONG".
  )
  ))
  data_set
  IN var_return
  FROM DUAL;
  
  
  RETURN var_return;
  END test_fnc;
  /
  < / pre >
  
  However, the specification of the ROWTYPE variable gives error ORA-00972 (except if I shorten the name of the item...):
  
  < pre >
  FUNCTION to CREATE or REPLACE test_fnc
  RETURN OF XMLTYPE
  AS
  var_return XMLTYPE.
  l_dummy DOUBLE % ROWTYPE;
  BEGIN
  SELECT dummy INTO l_dummy FROM DUAL;
  
  SELECT XMLCONCAT (XMLELEMENT)
  "TEST."
  XMLFOREST)
  l_dummy. Dummy "THIS_IS_OVER_30_CHARACTERS_LONG."
  )
  ))
  data_set
  IN var_return
  FROM DUAL;
  
  
  RETURN var_return;
  END test_fnc;
  /
  < / pre >
  
  Has anyone previously met, or have any ideas for a solution? I could specify all my variables as TYPE, but as there are many in the tables it would be easier to use ROWTYPE.
  
  Oracle Database 11 g Enterprise Edition Release 11.1.0.6.0 - 64 bit Production
  
  Thank you.

  This works if you add 'AS' after l_dummy.dummy

  SQL> CREATE OR REPLACE FUNCTION test_fnc
    2     RETURN XMLTYPE
    3  AS
    4     var_return   XMLTYPE;
    5     l_dummy      DUAL%ROWTYPE;
    6  BEGIN
    7     SELECT   dummy INTO l_dummy FROM DUAL;
    8
    9     SELECT   XMLCONCAT(XMLELEMENT (
   10                           "TEST",
   11                           XMLFOREST (
   12                              l_dummy.dummy AS "THIS_IS_OVER_30_CHARACTERS_LONG"
   13                           )
   14                        ))
   15                 data_set
   16       INTO   var_return
   17       FROM   DUAL;
   18  RETURN var_return;
   19  END test_fnc;
   20  /
  
  Function created.
  

  Ants

• 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.

• 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...

• fan stays on too long and the battery level decreases rapidly: any problem identified?

  Fan stays on too long and the battery level decreases rapidly: all identified cause problem or possible?

  MacBook Air mid-2013

  OS 10.11.13

  Processor 1.7 GHz Intel Core i7

  8 GB of DDR3 memory at 1600 MHz

  Thank you, Paolo

  Hi Paskowski,

  Can you give us a little more information about your problem?  What applications or processes are you using when you encounter the problem with your fan and battery?  The activity monitor application can provide you with some basic information.

  Use the monitor activity on your Mac.

  The resources below provides general information on how optimize the battery life and troubleshoot the battery on your MacBook Air.

  On batteries for laptops Mac

  Take care

• Identify too long to backup file names.

  Using Vista on my laptop and the complex file names are required because of the research that I do.

  When you run a regular backup to an external drive, I get an error message that some file names are too long for the files to copy, but no list of crime files is given.  I am informed to shorten them, but not how to identify them.
  Is there a quick way to find these files so that I can change the names?

  Hi John,.

  I just went to that link without problem using IE9 RC - but if you send you elsewhere to get the download, then maybe you'll have more success with the download page: http://www.parhelia-tools.com/products/pathscanner/Download.aspx.  It is the only near the top (or you can try the alternate).

  If specific filenames are not so long (assuming 260 is the number we need to worry and we are not quite sure of this), then it's probably the length of the path.  The path includes everything, like C:\Users\\Appdata\local\microsoft\temp\iooiee90939ntgngjoiga909ri4jt09049japgaopjgp\...\filename.doc and if this WHOLE thing is too long (260 or other), then it cannot copy or paste.  Chances are that these files were created by programs or automatically, not by you.

  My guess is that these are temporary files of IE (they tend to be very long) and if first delete you IE temporary files (Tools / Options / history / delete / don't check the Temp files and save them favorite boxes above, uncheck everything else for this test), then you find out that you don't really have the problem more.

  What is the external hard drive formatted in NTFS or FAT32 or FAT16?  If this isn't NTFS, I recommend that use the command convert to change to NTFS.  Not only is a better choice, but it can also solve this problem (although it's more a guess that based on specific research-, then it makes a difference with the size of the file and the file information, I saw say anything specifically made a difference in path length).  http://windows.microsoft.com/en-US/windows-vista/Convert-a-hard-disk-or-partition-to-NTFS-format.

  I hope this helps.

  Good luck!

• 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;