ETG throws ORA-12801, ORA-01652

Similar Questions

• several errors during the bulk add (ORA-13199, ORA-12801, ORA-01652-ORA-01653)

  Hello
  
  In a batch process, I use a big parallel add to insert millions of triples in an RDF model.
  At one point, an insert failed with this message:
  
  ORA-13199: DDL_same_rdf_indexes call failed: ORA-13199: step_num = 6 = ORA-12801 SQLERRM: error reported in the parallel query P020 Server
  ORA-01652: unable to extend segment temp of 128 in tablespace RDF dss = ALTER INDEX REBUILD PARTITION of 'RDF_LNK_SCPM_IDX' MODEL_63 NOLOGGING PARALLEL in LINE ORA-06512: at the 'MDSYS. MD", line 1723
  ORA-06512: at the 'MDSYS. MDERR", line 17
  ORA-06512: at the 'MDSYS. SDO_RDF_INTERNAL', line 9223
  ORA-06512: at the 'MDSYS. SDO_RDF_INTERNAL', line 9428
  ORA-06512: at the 'MDSYS. MD", line 1723
  ORA-06512: at the 'MDSYS. MDERR", line 17
  ORA-06512: at the 'MDSYS. SDO_RDF_INTERNAL', line 9441
  ORA-06512: at the 'MDSYS. SDO_RDF_INTERNAL', line 4255
  ORA-06512: at the 'MDSYS. SDO_RDF', line 276
  ORA-06512: at the 'MDSYS. RDF_APIS', line 693
  ORA-06512: at line 1
  
  Given that the batch continued and tried to insert later, I got this error twice, then another several times:
  
  ORA-13199: during the LBV:ORA - 01653: unable to extend table MDSYS. RDF$ TV_3F_1501FA303B1C4_56 of 128 in tablespace RDF ORA-06512: at the 'MDSYS. SDO_RDF_INTERNAL', line 1319
  ORA-06512: at the 'MDSYS. MD", line 1723
  ORA-06512: at the 'MDSYS. MDERR", line 17
  ORA-06512: at the 'MDSYS. SDO_RDF_INTERNAL", line 1414
  ORA-06512: at the 'MDSYS. SDO_RDF_INTERNAL', line 3786
  ORA-06512: at the 'MDSYS. SDO_RDF', line 276
  ORA-06512: at the 'MDSYS. RDF_APIS', line 693
  ORA-06512: at line 1
  
  Finally, later, inserting block worked without any errors. I don't have any sort of similar since errors.
  
  Any idea of what could have caused this?
  
  Thank you
  
  Kind regards
  Julien

  Indeed, it is a little uncertain. But here's a possibility (unless the tablepace has been extended before the retry):

  When several parallel processes are working on a query, each requires a space of sort. If N of them is active at a time and using their sorting max space requirements, the total space of necessary sorting can be beyond what is available in the temp tablespace. But, if we ever reach this point because some processes parallel either end early or have not reached the point where they need their sorting max spaces, then we can't hit it out of space error.

  Once again, an easy way to avoid this problem would be to use BIGFILE tablespaces or allocate enough space for relevant tablespaces.

• Configuring settings of data due to the error: ORA-12801 & ORA-01652

  Hello
  I have a configuration problem that I really need help because I understand almost nothing on oracle database management and I get errors:

  ORA-12801:error signaled in parallel query server P0XX
  ORA-01652:unable to extend temp segment by 128 in tablespace TEMPO1

  I have a server with this configuration:

  SO-HP-UX 
  Oracle: 10.2.0.3.0
  CPU’s -12
  Memory:24GB
  Temp01 tablespace: 20GB

  Some settings:

  Maximum sga memory is 20GB
  db_block_size  8192
  db_cache_size 2147483648
  db_file_multiblock_read_count              32
  db_name            RAID
  dml_locks           2000
  java_pool_size 0
  log_buffer          5242880
  max_enabled_roles      150
  nls_length_semantics   BYTE
  open_cursors   2000
  optimizer_mode             ALL_ROWS
  pga_aggregate_target  3221225472
  processes           2000
  query_rewrite_enabled              TRUE
  query_rewrite_integrity             trusted
  sessions              2205
  sga_max_size   21474836480
  shared_pool_size           117440512
  sort_area_size 65536
  undo_management      AUTO
  undo_retention              7200
  undo_tablespace            UNDOTBS1
  workarea_size_policy   AUTO

  the tables where created with nothing special, but I did an alter table to perform the following operations:

  alter table XPTO parallel (degree 11);

  When did I get this error:
  When I try to do a select with a NLSSORT (FIELD, ' nls_sort = binary "") AS "KEY1" and it return a few million lines.
  Based on this three items and a little more reading:

  http://www.dba-oracle.com/oracle_tips_sorts.htm
  http://www.dba-oracle.com/t_parallel_automatic_tuning_pat.htm
  http://www.dbasupport.com/oracle/ora10g/sorting_memory.shtml 

  Configure the following parameters with the values that I drove or I'm doing something really wrong?

  pga_aggregate_target = 18GB 
  _pga_max_size = 18GB 
  _smm_px_max_size = 5.4GB
  workarea_size_policy =AUTO
  increase TEMP01 to 40GB
  parallel_automatic_tuning=false

  Should I also create a new index for my paintings as:

  CREATE INDEX NlSSORT_index 

  ON my_table (NLSSORT (msisdn, 'nls_sort = binary')); due to this question? I got a clue: "msisdn, second_field ' who are a primary key for all fields.
  
  
  Thank you
  Ricardo Tomas

  You can leave at Oracle to decided the best degree of parallelism

  alter table XPTO parallel;
  

• ORA-01652: unable to extend temp segment

  Hello

  
  

  Chat support told me that I need to connect this question here...
  

  
  

  My cloud trial database service is running out of storage

  
  

  ORA-01652: unable to extend segment temp of 128 in tablespace APEX_ #.

  
  

  ORA-01653: unable to extend table YZJMXMYGKBNK. 128 in tablespace APEX_91669423895621749 CPC_STATEMENT

  
  

  I have 15 tables:

  
  

  Tablespace megabytes

  CPC_CONFIG APEX_ # 0.06

  CPC_CONTROL APEX_ # 0.06

  CPC_DEBUG APEX_ # 10.00

  CPC_EXTERNAL APEX_ # 0.81

  CPC_INDEX APEX_ # 0.13

  CPC_INPUTS APEX_ # 0.06

  CPC_STATEMENT APEX_ # 2.00

  CPC_STUDENT APEX_ # 0.06

  CPC_STUDENT_PAY APEX_ # 0.06

  CPC_STUDENT_STATEMENT APEX_ # 0.06

  DEPT APEX_ # 0.06

  EMP APEX_ # 0.06

  PAYPAL_SESSION_MAP APEX_ # 0.06

  PAYPAL_TRANSACTIONS APEX_ # 0.06

  RETURN APEX_ # 0.06

  
  

  How can I see what is using my storage?

  
  

  Thank you

  
  

  Steve
  

  
  

  Thanks Shema informing me run: Purge Recyclebin;

  My database is down to a low as 60 MB used.

• The Sky is Falling! ORA-01652: unable to extend segment by 128 temp

  So, we currently have a production problem, and I'm not so much aware as a java developer humble and not an expert of the Oracle.
  We continue to receive this error (below) when a certain heavy query hits the DB.
  Our DBA says that for "TABLE_SPACE_NAME_HERE" storage space is 20 GB of space and the problem is the query.
  The query has been works well for many months to many, but all of a sudden this a problem and we need to do something quick.
  We tried to bounce the application server, but the error came just at the time when the large select query gets hit.
  Any thoughts? Help! : )
  
  java.sql.SQLException: ORA-01652: unable to extend segment temp of 128 in tablespace TABLE_SPACE_NAME_HERE
  
  at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:113)
  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:754)
  at oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:219)
  at oracle.jdbc.driver.T4CPreparedStatement.executeForRows(T4CPreparedStatement.java:972)
  at oracle.jdbc.driver.OracleStatement.executeMaybeDescribe(OracleStatement.java:1074)
  at oracle.jdbc.driver.T4CPreparedStatement.executeMaybeDescribe(T4CPreparedStatement.java:854)
  at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1156)
  at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3415)
  at oracle.jdbc.driver.OraclePreparedStatement.executeQuery(OraclePreparedStatement.java:3460)
  at org.jboss.resource.adapter.jdbc.WrappedPreparedStatement.executeQuery(WrappedPreparedStatement.java:296)

  The error indicates that you have run out of space in your temporary tablespace.

  It is quite possible that the query plan has changed and that, for some reason, your query uses now a plan that is the cause to use radically more temporary for things like space sorts and hash joins that it was in the past. Depending on the version of Oracle, the authorized options, if Statspack is installed, etc as your DBA can probably look to see if the query plan for this statement has been modified. If it has, the DBA should be able to force Oracle to use the old query plan and probably need to investigate what caused the query plan to change first and resolve the underlying problem.

  It is also possible that the query itself is not using more space than normal temp, but the number of users (or their workload or of the volumns of data, with which they work) grew by causing the application to require more space in the temporary tablespace. If everyone does a kind of 10 MB and you have 2,000 concurrent users, you would use a total of 20 GB of temporary space. Try adding making 2001 the user a sort of 10 MB and now you're out of temporary space. Similarly, if the data volume has increased a little, you could go to have just enough space to be out of space.

  Justin

• ORA-01652: unable to extend temp by 1024 segment in tablespace AXPERT

  Dear team,
  While the import of the mistake .dmp file below shows. Please suggest me...
  
  
  ORA-39171: job knows a wait can be resumed.
  ORA-01652: unable to extend temp by 1024 segment in tablespace AXPERT
  ORA-39171: job knows a wait can be resumed.
  ORA-01652: unable to extend temp by 1024 segment in tablespace AXPERT

  What is the inability of a temp segment to expand has to do with "database security - general?

  Please lock this thread and open one in the appropriate forum, "General database".

  Thank you.

  When you include all the important, relevant information you have not provided here such as:
  1. version number
  2. what you import and how (IMP, DataPump, something else?)
  3. size and spatial arrangement in the temp tablespace and on autoextend?
  4. available for autoextend temp disk space?
  5. extract from the alert log showing the messages corresponding to the question.

• Unusual ORA-01652: unable to extend segment temp of 128 in tablespace TEMP_

  Hello gurus,
  
  I apologize with the same pot in different category
  
  I get a strange error, after current request for 15 minutes.
  

  ORA-01652: unable to extend temp segment by 128 in tablespace TEMP_TS
  01652. 00000 -  "unable to extend temp segment by %s in tablespace %s"
  *Cause:    Failed to allocate an extent of the required number of blocks for
             a temporary segment in the tablespace indicated.
  *Action:   Use ALTER TABLESPACE ADD DATAFILE statement to add one or more
             files to the tablespace indicated.

  select * from v$version;
  
  Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
  PL/SQL Release 11.2.0.3.0 - Production
  "CORE     11.2.0.3.0     Production"
  TNS for IBM/AIX RISC System/6000: Version 11.2.0.3.0 - Production
  NLSRTL Version 11.2.0.3.0 – Production

  After the series of suggestions online I increased 10Gig TEMP_TS since I got the same error a few times more.
  
  I have other databases with the same data in which I have less temporary space (5 Gig), but it not start error and results less than 1 sec.
  
  I bounce the database, see if it makes a difference, but it did not.
  
  My question is
  
  * 1. What are the other settings I need to account for this mistake? *
  * 2. Why, even after the increase in temp space (almost double) has not solved the error? *

  Good article to verify what it takes when temp tablespace runs out of the question:

  http://www.dbspecialists.com/files/presentations/temp_space.html

• ORA-01652: unable to extend temp segment of 64 in tablespace

  Hello
  
  I get the error ORA-01652: unable to extend temp segment of 64 in tablespace < nom_tablespace >. I checked the temp tablespace and temporary table space space is sufficiently free.
  
  A pls you suggest on this.
  
  
  Thank you

  Salvation;

  Please see below note that might be useful for your question:

  TROUBLESHOOTING GUIDE (TSG) - IMPOSSIBLE to EXTEND errors [ID 1025288.6]

  Respect of
  HELIOS

• [10g XE] ORA-01652... Can I change the tablespace?

  My apologies if the questions to ask to seem silly... I'm not used to manage a database; I'm really only familiar with a database query, but I XE (10g) installed on my local machine as my test environment, and I came across a problem today that I have not been able to understand yet on my own like...
  
  There, I created a username for me to use, so I wasn't just connecting as sys all the time. (I hear this is a bad thing, but for a small test environment of XE, I don't know how important that is.) Earlier this morning, I tried to create a table such as selecting a remote (via a database link) when I got an ORA-01652 error. He said, 'impossible to extend segment by 1028 temp in the SYSTEM tablespace. I didn't know why he tried to use the SYSTEM tablespace, but I took a peek, and it turns out that all the tables I have create under my username gets stuck in the SYSTEM tablespace.
  
  I did some research and found:

  CREATE TABLESPACE mytbs1
  DATAFILE '/u01/oracle/data/mytbs01.dbf' SIZE 500M
  EXTENT MANAGEMENT LOCAL
  SEGMENT SPACE MANAGEMENT AUTO;

  to create a tablespace, so I did that, it's 1 GB, but then I couldn't figure out how to make my username use always this tablespace.
  
  Also, I saw that I have a file temp.dbf, which is only 20 MB, and I wanted to make sure that my user name that was used as its temp tablespace, so I found this piece of code:

  ALTER USER <user_account> SET TEMPORARY TABLESPACE <temp_tbsp>

  and tried to use it for my temp temp tablespace, but I got ORA-00922: missing or invalid option (with SET indicated that the problem).
  
  In addition, moreover, if I find that 20 MB is not big enough for my temp space, how to extend that?
  
  
  Thanks in advance!

  Hello

  user11033437 wrote:

  
  SYS@XE 09-23-2010 09:08:01> alter user myusername set temporary tablespace temp;
  alter user myusername set temporary tablespace temp
  *
  ERROR at line 1:
  ORA-00922: missing or invalid option
  

  Search for the correct syntax in the SQL reference manual. (Lose 'SET').

  Get used to using textbooks.
  You can memorize the syntax for the commands and features that you use every day, but there's always a lot of things you do only from time to time. (You'll probably be creating or editing users only from time to time.)

• hash with very large internal table plan causes ORA-01652

  Hello
  
  We have a select with dubious plan:
  
  SELECT * FROM T1 where T1. F1 in (select T2. F1 T2)
  
  Plan:
  | ID | Operation | Name | Lines | Bytes | TempSpc | Cost |
  | 0 | SELECT STATEMENT | 59 M | 12G | 1 401 K |
  | 1. SEMI HASH JOIN | 59 M | 12G | 55G | 1 401 K |
  | 2. TABLE ACCESS FULL | T1 | 260 M | 52G | 489K |
  | 3. TABLE ACCESS FULL | T2 | 209K | 1843K | 84.
  
  As you see a record 260 million (52 GB) T1 and T2 has approximately 200,000 records (approximately 2 MB)
  Oracle chooses the hash with T1 inner table join. Thus all T1 is tempted to read first in memory.
  And when the memory is full, the TEMP tablespace is filled.
  And because the TEMP tablespace is less than 55 GB, an error has occurred:
  ORA-01652: unable to extend segment temp of 128 in tablespace TEMP
  
  Question:
  Why oracle choose the hash with inner table so big join?
  And how can we solve this problem?
  
  Other notes:
  T1 and T2 is analyzed today.
  Presumably no index or table.
  The database is Oracle 9i Enterprise.
  Description of Oracle 9i hash (first there are more small table as you can see):
  http://download.Oracle.com/docs/CD/B10501_01/server.920/a96533/optimops.htm#76074
  
  THX: sides.

  Hello

  Oracle 9i cannot make HASH JOIN RIGHT SEMI - were introduced in 10g.

  ----------------------------------------------------------------------------------------------------------------------------
  | Id  | Operation             | Name | Starts | E-Rows | A-Rows |   A-Time   | Buffers | Reads  |  OMem |  1Mem | Used-Mem |
  ----------------------------------------------------------------------------------------------------------------------------
  |   0 | SELECT STATEMENT      |      |      1 |        |      1 |00:00:55.73 |     162K|    162K|       |       |          |
  |   1 |  SORT AGGREGATE       |      |      1 |      1 |      1 |00:00:55.73 |     162K|    162K|       |       |          |
  |*  2 |   HASH JOIN RIGHT SEMI|      |      1 |   8147 |      0 |00:00:55.73 |     162K|    162K|   988K|   988K| 1031K (0)|
  |   3 |    TABLE ACCESS FULL  | T2   |      1 |     18 |     18 |00:00:00.01 |       3 |      0 |       |       |          |
  |   4 |    TABLE ACCESS FULL  | T    |      1 |     11M|     11M|00:02:09.99 |     162K|    162K|       |       |          |
  ----------------------------------------------------------------------------------------------------------------------------
  
  Predicate Information (identified by operation id):
  ---------------------------------------------------
  
     2 - access("OBJECT_NAME"="USERNAME")
  

• ORA-01652: unable to extend segment temp of 128 in tablespace TEMP2

  Hello
  
  I get this error when I run the SQL query is mentioned below
  
  SELECT
  PRO_ID,
  POBJ_ID,
  MPRO_ID,
  MPOBJ_ID,
  MAX (REUSE_OTHER_SOURCE) REUSE_OTHER_SOURCE
  
  Of
  (
  Select
  PRO_ID,
  POBJ_ID,
  MPRO_ID,
  MPOBJ_ID,
  REUSE_OTHER_SOURCE,
  PROJECT NAME,
  INDUSTRY_CATEGORY,
  APPLICATION_MODULE,
  NOTATION,
  REUSE_PERCENTAGE,
  REUSE_DETAILS,
  UPDATED_DATE,
  UPDATED_BY,
  STATUS
  of LEVERAGE_TEMP_save
  
  UNION ALL
  
  Select
  Pro.ID,
  pobj.ID,
  MO. MITRA_PRO_ID,
  MO. MITRA_POBJ_ID,
  REUSE_OTHER_SOURCE NULL,
  PROJECT NAME NULL,
  INDUSTRY_CATEGORY NULL,
  APPLICATION_MODULE NULL,
  SIDE OF NULL,
  REUSE_PERCENTAGE NULL,
  REUSE_DETAILS NULL,
  UPDATED_DATE NULL,
  UPDATED_BY NULL,
  NULL STATE
  Of
  Mitra_objects MO,
  project_objects pobj,
  pro projects,
  XXMI_PROJECT_MASTER_ALL@NAIO_TO_MITRA MPRO, INV.
  XXMI_PROJECT_OBJECTS_ALL@NAIO_TO_MITRA MPOBJ,
  FND_LOOKUP_VALUES_VL@NAIO_TO_MITRA FL
  )
  
  
  PRO_ID GROUP,
  POBJ_ID,
  MPRO_ID,
  MPOBJ_ID
  
  
  When I run I get this error message
  
  ORA-01652: unable to extend segment temp of 128 in tablespace TEMP2
  
  Please sugggest me how to solve this problem.
  
  
  Thank you
  Sudhir

  You do a Cartesian join plus 6 (six!) tables in the second
  one part of the union any section. (Probably a where clause clause is missin here.)

  If you multiply the record number of these tables
  You can estimate how large your temporary segments should be.

  URS

• ORA-01652: unable to extend segment temp of 128 in tablespace TEMP

  Hello friends,
  
  I get this alert in the alert log every time that the statistics of the work... Here is the complete list of the alerts log
  

  78939:ORA-12012: error on auto execute of job 2
  78940:ORA-01652: unable to extend temp segment by 128 in tablespace TEMP
  78941:ORA-06512: at "SYS.DBMS_STATS", line 13336
  78942:ORA-06512: at "SYS.DBMS_STATS", line 13682
  78943:ORA-06512: at "SYS.DBMS_STATS", line 13760
  78944:ORA-06512: at "SYS.DBMS_STATS", line 13719
  78945:ORA-06512: at line 1

  Please advise... How to fix this error

  Please advise... How to fix this error

  ALTER TABLESPACE TEMP ADD TEMPFILE...

  View the name of the operating system (OS) & version for DB Server System.
  View the results of
  SELECT * from version $ v

  Published by: sb92075 on December 25, 2009 19:40

• ORA-01652 in Tablespace TEMP

  Hello
  
  We get the following errors:
  
  RMAN > overlap archivelog all;
  
  
  
  from full resynchronization of the recovery catalog
  
  RMAN-00571: ===========================================================
  
  RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
  
  RMAN-00571: ===========================================================
  
  RMAN-03002: failure of command of overlap at 2009-01-07 14:26:10
  
  RMAN-03014: implicit recovery catalog Resync failed
  
  RMAN-03009: resync command failed complete default channel at 2009-01-07 14:26:10
  
  ORA-01652: unable to extend segment in tablespace temp
  
  
  
  RMAN >
  
  We tried to increase the size of the TEMP tablespace, but this operation keeps using the set temp tablespace. It's the temp tablespace in the target database that fills.
  We cannot continue to increase the size of the ts TEMP to fill the disk.
  We also tried to create a new repository, but it had the same result.
  
  I think that there is something in the database tables, as one of our backups used the control target as its repository file. Should I remove the entries in these tables in the tablespace target to make the repository think that there is no re-synchronization to do?
  
  Kind regards
  Tim.

  See this metalink note:

  Record from database in RMAN fails with RMAN-03002, RMAN-03014 and ORA-01652
  DOC - ID: 469327.1

  Even if you run another command, the error of the battery is exactly the same.

  Werner

• Procedure throwing ORA-01002: sequence error recovery

  Hello..
  I do not use any commits inside sliders with update instructions. He was a candidate in the last 48 hrs and throws errors suddenly began. Can someone help me why it has sporadic problems. Code is inserted here.
  
  Is Sys_refcursor a dynamic cursor...? I have my transaction_cursor as a sys_refcursor? What's the problem here. If Yes, do I have to remove commit within the opening and closing of this slider. The validation is performed for each 10000 lines...
  
  Thanks in advance
  Kris
  
  PROCEDURE PROCESS_EXECUTOR AS
  
  cursor jobs_cursor is
  Select job_id in)
  SELECT DISTINCT
  job_id
  FROM table_x)
  ORDER BY job_id) where ROWNUM < = 10;
  
  transaction_cursor SYS_REFCURSOR;
  TRAN tran_type;
  
  sql_code varchar2 (1024);
  err_msg varchar2 (1024);
  
  cmt_counter number: = 0;
  
  
  BEGIN - beginning of Process_Executor
  
  
  for r_csr loop jobs_cursor
  Transaction_cursor OPEN for SELECT * FROM table_y a
  WHERE a.job_id = r_csr.job_id
  order of create_timestamp, task_id;
  LOOP
  Get the transaction_cursor COLLECT LOOSE tran LIMIT 10;
  Take the EXIT WHEN tran. COUNT = 0;
  
  
  
  BECAUSE me IN 1.tran. COUNTING LOOP
  Start
  
  If cmt_counter = 0 then
  SAVEPOINT last_transaction;
  end if;
  
  cmt_counter: = cmt_counter + 1;
  
  
  exec_process1 (TRAN (i));
  
  If (cmt_counter = 10000) then
  commit;
  cmt_counter: = 0;
  end if;
  
  
  exception
  while others then
  back to last_transaction;
  end;
  END LOOP;
  
  END LOOP;
  CLOSE Transaction_cursor;
  
  end loop;
  
  
  commit;
  
  
  END PROCESS_EXECUTOR;

  No idea what you're trying to do really, especially with no detail about what "exec_process1" is.

  Be aware though that COMMIT / ROLLBACK within SELECT... UPDATE IS not the only cause of ORA-01002, unqualified rollback or rollback to the point of backup before opening a cursor also causes this error.

  Oracle Database 10g Express Edition Release 10.2.0.1.0 - Production
  
  SQL> DECLARE
    2     CURSOR c_emp
    3     IS
    4        SELECT e.*
    5        FROM   emps e;
    6
    7     r_emp c_emp%ROWTYPE;
    8  BEGIN
    9     UPDATE emps
   10        SET ename = ename;
   11
   12     OPEN c_emp;
   13
   14     FETCH c_emp
   15     INTO  r_emp;
   16
   17     ROLLBACK;
   18
   19     FETCH c_emp
   20     INTO  r_emp;
   21  END;
   22  /
  DECLARE
  *
  ERROR at line 1:
  ORA-01002: fetch out of sequence
  ORA-06512: at line 19
  
  SQL> DECLARE
    2     CURSOR c_emp
    3     IS
    4        SELECT e.*
    5        FROM   emps e;
    6
    7     r_emp c_emp%ROWTYPE;
    8  BEGIN
    9     SAVEPOINT savepoint_name;
   10
   11     UPDATE emps
   12        SET ename = ename;
   13
   14     OPEN c_emp;
   15
   16     FETCH c_emp
   17     INTO  r_emp;
   18
   19     ROLLBACK TO savepoint_name;
   20
   21     FETCH c_emp
   22     INTO  r_emp;
   23  END;
   24  /
  DECLARE
  *
  ERROR at line 1:
  ORA-01002: fetch out of sequence
  ORA-06512: at line 21
  
  SQL>
  

• apex_json throws ORA-06502

  Hello

  I use 5 APEX and must work with GEOJSON.

  If I test the following statement in SQL Developer, everything works fine:

  DECLARE
      s varchar2(32767) := '{ "a": 1, "b": ["hello", "world"]}';
  BEGIN
      apex_json.parse(s);
      sys.dbms_output.put_line('a is '||apex_json.get_varchar2(p_path => 'a'));
  END;
  

  But if I change the JSON data to the following:

  s varchar2(32767) := '{ "a": 1.1, "b": ["hello", "world"]}';
  

  I get this error:

  Fehler beim Start in Zeile : 1 in Befehl -
  DECLARE
      s varchar2(32767) := '{ "a": 1.1, "b": ["hello", "world"]}';
  BEGIN
      apex_json.parse(s);
      sys.dbms_output.put_line('a is '||apex_json.get_varchar2(p_path => 'a'));
  END;
  Fehlerbericht -
  ORA-06502: PL/SQL: numerischer oder Wertefehler: Fehler beim Konvertieren von Zeichen zu Zahl
  ORA-06512: in "APEX_050000.WWV_FLOW_JSON", Zeile 367
  ORA-06512: in "APEX_050000.WWV_FLOW_JSON", Zeile 519
  ORA-06512: in "APEX_050000.WWV_FLOW_JSON", Zeile 566
  ORA-06512: in "APEX_050000.WWV_FLOW_JSON", Zeile 756
  ORA-06512: in "APEX_050000.WWV_FLOW_JSON", Zeile 774
  ORA-06512: in "APEX_050000.WWV_FLOW_JSON", Zeile 811
  ORA-06512: in "APEX_050000.WWV_FLOW_JSON", Zeile 839
  ORA-06512: in "APEX_050000.WWV_FLOW_JSON", Zeile 852
  ORA-06512: in Zeile 4
  06502. 00000 -  "PL/SQL: numeric or value error%s"
  *Cause:    
  *Action:
  

  The same thing happens with with MyMethod...

  sys.dbms_output.put_line('a is '||apex_json.get_number(p_path => 'a'));
  

  Because I work with GEOJSON, there are decimal numbers in my JSON data - I have to deal with.

  I have not found any suspicion in the apex_json documentation.

  How can I solve this problem?

  Kind regards

  Christian

  Hello

  your example works fine for me on 5.0.2. There were a few bugs that fixed us since 5.0. Some may be available as SAFF, but maybe you need to upgrade to the latest version.

  Kind regards

  Christian