OR-SCOPE-223409 error

I got an error in the driver OR-SCOPE (version 4.1.3), using the NOR-5122 digitizer. The error is died in the niScope_SendSoftwareTriggerEdge function. The relevant sequence of commands that I send is:

Secret = niScope_Abort (SessionID);

Secret = niScope_ConfigureHorizontalTiming (SessionID, 380E6, 256, 0.0, 1, VI_FALSE);

Secret = niScope_ConfigureTriggerEdge (SessionID, "0", 0,0, NISCOPE_VAL_POSITIVE, NISCOPE_VAL_DC, 0.0, 0.0);

Secret = niScope_ConfigureChanCharacteristics (SessionID, '0', NISCOPE_VAL_50_OHMS, 0,0);

Secret = niScope_ConfigureVertical (SessionID, "0", 0.2, 0.0, NISCOPE_VAL_DC, 1.0, VI_TRUE);

Secret = niScope_InitiateAcquisition (SessionID);

Secret = niScope_SendSoftwareTriggerEdge (SessionID, NISCOPE_VAL_SOFTWARE_TRIGGER_REFERENCE);       Secret = 223409

The return of niScope_errorHandler is:

Error FFFC974F.


Possible reasons:

Internal software error has occurred in the extended software. Please contact the support of National Instruments.


Name of the component: nihsdrk

File name: \Measurements\highSpeedDigitizers\hsd\driver\trunk\4.1.1\source\kernelPrimitive\tMacroSupervisor.cpp

Line number: 716


Source:

    unknown (0)?:

    unknown (0)?:

    unknown (0)?:

    unknown (0)?:

    unknown (0)?:

    unknown (0)?:

    unknown (0)?:

    unknown (0)?:

    unknown (0)?:

    unknown (0)?:


State code:-223409

The error will not occur if I call niScope_close and niScope_init after every acquisition, but I guess I should not have done that.

Hi rings,

It is a known issue, you're right that you shouldn't call niScope_close and niScope_init each time, but for now, this is the best solution.

Tags: NI Hardware

Similar Questions

  • Bounded gets dialog task flow that The ADF tent last pop entry scope page error stack flow controller

    I have a flow of stubborn task that I throw like a line-popup dialog box.  There are buttons with an action listener.  When I use AdfFacesContext.getCurrentInstance () .returnFromDialog (returnValue, null) at the end of the code in the event the message I get is

    ADFC 12001: The ADF controller pop tent last entry of error in page flow scope stack.

    The error is displayed in the debug window, but does not stop the application or display the message in the application.

    I use JDev 11.1.1.7

    Everything seems to work, why so this error occurring?

    I've seen this error, but no clear answer-related positions.

    Hello

    seems that the workflow is trying to clean up but there is nothing to clean up. I can't find any entry in the database of bugs, but think it's because the workflow in fact - if present in a dialog online - is not stacked.

    Frank

  • Error in the oracle database after you set the "Compatible" setting to lower

    Hello
    Windows 2008 server
    Oracle 11.2.0.3.0

    I just put changed the parameter system compatible on my database (import to a lower version - 10g) and attempted to restart and my database does not open now.
    Pls help, what shape I do now? !
    Here's what I've done?
    (Given that the mentioned documentation that I have to restart the database for the compatible parameter is taken into account, I did.)
    SQL> alter system set compatible='10.1.0.0.0' scope=spfile;

System altered.

SQL> show parameter compatible
(still showing same)

NAME                                 TYPE        VALUE
------------------------------------ ----------- ------------------------------
compatible                           string      11.2.0.0.0

So, restart!
SQL> shutdown immediate
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> startup open
ORACLE instance started.

Total System Global Area 1720328192 bytes
Fixed Size                  2255904 bytes
Variable Size            1174406112 bytes
Database Buffers          536870912 bytes
Redo Buffers                6795264 bytes
ORA-00201: control file version 11.2.0.0.0 incompatible with ORACLE version
10.1.0.0.0
ORA-00202: control file: 'F:\ORACLE11G\ORADATA\GEOOAP\GEOOAP\CONTROL01.CTL'

SQL> alter system set compatible='11.2.0.0.0' scope=spfile;
alter system set compatible='11.2.0.0.0' scope=spfile
*
ERROR at line 1:
ORA-32012: SPFILE format is inconsistent with value of COMPATIBLE parameter


SQL> shutdown immediate;
ORA-01507: database not mounted

ORACLE instance shut down.

SQL> startup mount;
ORACLE instance started.

Total System Global Area 1720328192 bytes
Fixed Size                  2255904 bytes
Variable Size            1174406112 bytes
Database Buffers          536870912 bytes
Redo Buffers                6795264 bytes
ORA-00201: control file version 11.2.0.0.0 incompatible with ORACLE version
10.1.0.0.0
ORA-00202: control file: 'F:\ORACLE11G\ORADATA\GEOOAP\GEOOAP\CONTROL01.CTL'
    Pls help to fix... its very urgent.

    Emmanuel says:
    Hello
    Windows 2008 server
    Oracle 11.2.0.3.0

    I just put changed the parameter system compatible on my database (import to a lower version - 10g) & tried to restart and my database does not open now.
    Pls help, what shape I do now? !
    Here's what I've done?
    (Given that the mentioned documentation that I have to restart the database for the compatible parameter is taken into account, I did.)

    SQL> alter system set compatible='10.1.0.0.0' scope=spfile;

System altered.

SQL> show parameter compatible
(still showing same)

NAME                                 TYPE        VALUE
------------------------------------ ----------- ------------------------------
compatible                           string      11.2.0.0.0

So, restart!
SQL> shutdown immediate
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> startup open
ORACLE instance started.

Total System Global Area 1720328192 bytes
Fixed Size                  2255904 bytes
Variable Size            1174406112 bytes
Database Buffers          536870912 bytes
Redo Buffers                6795264 bytes
ORA-00201: control file version 11.2.0.0.0 incompatible with ORACLE version
10.1.0.0.0
ORA-00202: control file: 'F:\ORACLE11G\ORADATA\GEOOAP\GEOOAP\CONTROL01.CTL'

SQL> alter system set compatible='11.2.0.0.0' scope=spfile;
alter system set compatible='11.2.0.0.0' scope=spfile
*
ERROR at line 1:
ORA-32012: SPFILE format is inconsistent with value of COMPATIBLE parameter

SQL> shutdown immediate;
ORA-01507: database not mounted

ORACLE instance shut down.

SQL> startup mount;
ORACLE instance started.

Total System Global Area 1720328192 bytes
Fixed Size                  2255904 bytes
Variable Size            1174406112 bytes
Database Buffers          536870912 bytes
Redo Buffers                6795264 bytes
ORA-00201: control file version 11.2.0.0.0 incompatible with ORACLE version
10.1.0.0.0
ORA-00202: control file: 'F:\ORACLE11G\ORADATA\GEOOAP\GEOOAP\CONTROL01.CTL'

    Pls help to fix... its very urgent.

    It is a forum for peer volunteers. There is no "urgent" here. For "urgent", you open a sev-1 SR with Oracle's Support.

    That said, what I would do at this point is to create a your spfile init.ora file, and then edit this file init.ora to set the compatible parameter to where it should be, create a file the init.ora spfile and restart db.

    Assuming your sid is "geooap":

    copy spfilegeooap.ora spfilegeooap.save
set ORACLE_SID=geooapp
sqlplus /nolog
create pfile='initgeooap.ora' from spfile;
exit
notepad initgeooap.ora  << fix the parameter
sqlplus /nolog
create spfile from pfile='initgeooap.ora';
startup

  • Using DB_RECOVERY_FILE_DEST and LOG_ARCHIVE_DEST - error ORA-16019

    Hello

    My database is currently configured to write files archivelog on two sites: / u01/app/oracle/archivelogs (which is the log_archive_dest parameter and is ranked number 1) and USE_DB_RECOVERY_FILE_DEST (10), which is
    under/u01/app/oracle/flash_recovery_area. I want to spend the two locations for separate discs.

    When I attempt to move or the other, I get the following errors:


    SQL > ALTER SYSTEM SET DB_RECOVERY_FILE_DEST = ' / u03/fra/MYDB/flash_recovery_area "SCOPE = BOTH;
    ALTER SYSTEM SET DB_RECOVERY_FILE_DEST = ' / u03/fra/MYDB/flash_recovery_area "SCOPE = BOTH
    *
    ERROR on line 1:
    ORA-02097: the parameter cannot be changed because specified value is not valid
    ORA-16019: cannot use db_recovery_file_dest with LOG_ARCHIVE_DEST or LOG_ARCHIVE_DUPLEX_DEST

    SQL > alter system set log_archive_dest = "/ u02/archive/MYDB";
    ALTER system set log_archive_dest = "/ u02/archive/MYDB '.
    *
    ERROR on line 1:
    ORA-02097: the parameter cannot be changed because specified value is not valid
    ORA-16018: cannot use LOG_ARCHIVE_DEST with LOG_ARCHIVE_DEST_n or DB_RECOVERY_FILE_DEST


    Any ideas?

    Thanks for any help.

    cool, finally you got. Thanks for pasting of output.

    Barry K.

  • Question about SET log_buffer and SCOPE = SPFILE

    Good evening

    I am teacher Oracle. In the book I use it says that I have to specify the SCOPE = SPFILE in order (because it is a static parameter):
    alter system set log_buffer = 6m scope=SPFILE;
    It is said that if I specify the scope as indicated, the command will succeed, but I still get the error:
    SQL> alter system set log_buffer = 6M scope=SPFILE;

alter system set log_buffer = 6M scope=SPFILE
                 *
ERROR at line 1:
ORA-02095: specified initialization parameter cannot be modified


SQL> show user
USER is "SYS"
SQL>
    I am logged in as "SYS as SYSDBA.

    My question is: why it is not working? (the book says it should).

    Thank you for your help,

    John. 
    SQL> alter system set log_buffer=7249920 scope=spfile;

System altered.

    It works for me.

  • political error of creation of the fga

    SQL > start
    (2 dbms_fga.add_policy)
    3 object_schema = > "SA."
    object_name 4 = > "TABLE_CASE"
    5 policy_name = > "SA_Audit"
    6 audit_condition = > 'status = "A" '.
    7 audit_column = > 'OBJID, S_TITLE, CASE_STATE2CONDITION. "
    8 handler_schema = > "SA."
    9 handler_module = > "FGA_HANDLER"
    10 activate = > TRUE,
    11 statement_types = > ' SELECT, UPDATE.
    12 audit_trail = > DBMS_FGA. DB + EXTENDED,
    13 audit_column_opts = > dbms_fga.all_columns);
    14 end;
    15.
    AUDIT_TRAIL = > DBMS_FGA. DB + EXTENDED,
    *
    ERROR on line 12:
    ORA-06550: line 12, column 1:
    PLS-00103: encountered the symbol "AUDIT_TRAIL" when awaits an of the
    Next:
    ), * & = - + <>/ is mod remains not rem
    < an exponent (*) > <>or! = or ~ = > = < = <>and or LIKE2_
    LIKE4_ LIKEC_ between | Member of multiset SUBMULTISET_
    The symbol ',' was replaced by "AUDIT_TRAIL" continue.


    SQL >
    SQL > start
    (2 dbms_fga.add_policy)
    3 object_schema = > "SA."
    object_name 4 = > "TABLE_CASE"
    5 policy_name = > "SA_Audit"
    6 audit_condition = > 'status = "A" '.
    7 audit_column = > 'OBJID, S_TITLE, CASE_STATE2CONDITION. "
    8 handler_schema = > "SA."
    9 handler_module = > "FGA_HANDLER"
    10 activate = > TRUE,
    11 statement_types = > ' SELECT, UPDATE.
    12 audit_trail = > DBMS_FGA. DB_EXTENDED,
    13 audit_column_opts = > dbms_fga.all_columns);
    14 end;
    15.
    AUDIT_TRAIL = > DBMS_FGA. DB_EXTENDED,
    *
    ERROR on line 12:
    ORA-06550: line 12, column 1:
    PLS-00103: encountered the symbol "AUDIT_TRAIL" when awaits an of the
    Next:
    ), * & = - + <>/ is mod remains not rem
    < an exponent (*) > <>or! = or ~ = > = < = <>and or LIKE2_
    LIKE4_ LIKEC_ between | Member of multiset SUBMULTISET_
    The symbol ',' was replaced by "AUDIT_TRAIL" continue.


    SQL > start
    (2 dbms_fga.add_policy)
    3 object_schema = > "SA."
    object_name 4 = > "TABLE_CASE"
    5 policy_name = > "SA_Audit"
    6 audit_condition = > 'status = "A" '.
    7 audit_column = > 'OBJID, S_TITLE, CASE_STATE2CONDITION. "
    8 handler_schema = > "SA."
    9 handler_module = > "FGA_HANDLER"
    10 activate = > TRUE,
    11 statement_types = > ' SELECT, UPDATE.
    12 audit_trail = > ' DBMS_FGA. SCOPES '.
    13 audit_column_opts = > dbms_fga.all_columns);
    14 end;
    15.
    AUDIT_TRAIL = > ' DBMS_FGA. SCOPES '.
    *
    ERROR on line 12:
    ORA-06550: line 12, column 1:
    PLS-00103: encountered the symbol "AUDIT_TRAIL" when awaits an of the
    Next:
    ), * & = - + <>/ is mod remains not rem
    < an exponent (*) > <>or! = or ~ = > = < = <>and or LIKE2_
    LIKE4_ LIKEC_ between | Member of multiset SUBMULTISET_
    The symbol ',' was replaced by "AUDIT_TRAIL" continue.


    SQL >
    SQL > start
    (2 dbms_fga.add_policy)
    3 object_schema = > "SA."
    object_name 4 = > "TABLE_CASE"
    5 policy_name = > "SA_Audit"
    6 audit_condition = > 'status = "A" '.
    7 audit_column = > 'OBJID, S_TITLE, CASE_STATE2CONDITION. "
    8 handler_schema = > "SA."
    9 handler_module = > "FGA_HANDLER"
    10 activate = > TRUE,
    11 statement_types = > ' SELECT, UPDATE.
    12 audit_trail = > DBMS_FGA. EXTENDED,
    13 audit_column_opts = > dbms_fga.all_columns);
    14 end;
    15.
    AUDIT_TRAIL = > DBMS_FGA. EXTENDED,
    *
    ERROR on line 12:
    ORA-06550: line 12, column 1:
    PLS-00103: encountered the symbol "AUDIT_TRAIL" when awaits an of the
    Next:
    ), * & = - + <>/ is mod remains not rem
    < an exponent (*) > <>or! = or ~ = > = < = <>and or LIKE2_
    LIKE4_ LIKEC_ between | Member of multiset SUBMULTISET_
    The symbol ',' was replaced by "AUDIT_TRAIL" continue.


    SQL > start
    (2 dbms_fga.add_policy)
    3 object_schema = > "SA."
    object_name 4 = > "TABLE_CASE"
    5 policy_name = > "SA_Audit"
    6 audit_condition = > 'status = "A" '.
    7 audit_column = > 'OBJID, S_TITLE, CASE_STATE2CONDITION. "
    8 handler_schema = > "SA."
    9 handler_module = > "FGA_HANDLER"
    10 activate = > TRUE,
    11 statement_types = > ' SELECT, UPDATE.
    12 audit_trail = > DBMS_FGA + EXTENDED,.
    13 audit_column_opts = > dbms_fga.all_columns);
    14 end;
    15.
    AUDIT_TRAIL = > DBMS_FGA + EXTENDED,.
    *
    ERROR on line 12:
    ORA-06550: line 12, column 1:
    PLS-00103: encountered the symbol "AUDIT_TRAIL" when awaits an of the
    Next:
    ), * & = - + <>/ is mod remains not rem
    < an exponent (*) > <>or! = or ~ = > = < = <>and or LIKE2_
    LIKE4_ LIKEC_ between | Member of multiset SUBMULTISET_
    The symbol ',' was replaced by "AUDIT_TRAIL" continue.


    SQL >
    SQL > start
    (2 dbms_fga.add_policy)
    3 object_schema = > "SA."
    object_name 4 = > "TABLE_CASE"
    5 policy_name = > "SA_Audit"
    6 audit_condition = > 'status = "A" '.
    7 audit_column = > 'OBJID, S_TITLE, CASE_STATE2CONDITION. "
    8 handler_schema = > "SA."
    9 handler_module = > "FGA_HANDLER"
    10 activate = > TRUE,
    11 statement_types = > ' SELECT, UPDATE.
    audit_trail 12 = > "EXTENDED."
    13 audit_column_opts = > dbms_fga.all_columns);
    14 end;
    15.
    AUDIT_TRAIL = > "EXTENDED."
    *
    ERROR on line 12:
    ORA-06550: line 12, column 1:
    PLS-00103: encountered the symbol "AUDIT_TRAIL" when awaits an of the
    Next:
    ), * & = - + <>/ is mod remains not rem
    < an exponent (*) > <>or! = or ~ = > = < = <>and or LIKE2_
    LIKE4_ LIKEC_ between | Member of multiset SUBMULTISET_
    The symbol ',' was replaced by "AUDIT_TRAIL" continue.


    SQL >
    SQL > start
    (2 dbms_fga.add_policy)
    3 object_schema = > "SA."
    object_name 4 = > "TABLE_CASE"
    5 policy_name = > "SA_Audit"
    6 audit_condition = > 'status = "A" '.
    7 audit_column = > 'OBJID, S_TITLE, CASE_STATE2CONDITION. "
    8 handler_schema = > "SA."
    9 handler_module = > "FGA_HANDLER"
    10 activate = > TRUE,
    11 statement_types = > ' SELECT, UPDATE.
    audit_trail 12 = > "EXTENDED."
    13 audit_column_opts = > dbms_fga.all_columns);
    14 end;
    15.
    AUDIT_TRAIL = > "EXTENDED."
    *
    ERROR on line 12:
    ORA-06550: line 12, column 1:
    PLS-00103: encountered the symbol "AUDIT_TRAIL" when awaits an of the
    Next:
    ), * & = - + <>/ is mod remains not rem
    < an exponent (*) > <>or! = or ~ = > = < = <>and or LIKE2_
    LIKE4_ LIKEC_ between | Member of multiset SUBMULTISET_
    The symbol ',' was replaced by "AUDIT_TRAIL" continue.


    SQL >
    SQL > start
    (2 dbms_fga.add_policy)
    3 object_schema = > "SA."
    object_name 4 = > "TABLE_CASE"
    5 policy_name = > "SA_Audit"
    6 audit_condition = > 'status = "A" '.
    7 audit_column = > 'OBJID, S_TITLE, CASE_STATE2CONDITION. "
    8 handler_schema = > "SA."
    9 handler_module = > "FGA_HANDLER"
    10 activate = > TRUE,
    11 statement_types = > ' SELECT, UPDATE.
    12 audit_column_opts = > dbms_fga.all_columns);
    13 end;
    14.
    audit_column_opts = > dbms_fga.all_columns);
    *
    ERROR on line 12:
    ORA-06550: line 12, column 1:
    PLS-00103: encountered the symbol "AUDIT_COLUMN_OPTS" when awaits an of the
    Next:
    ), * & = - + <>/ is mod remains not rem
    < an exponent (*) > <>or! = or ~ = > = < = <>and or LIKE2_
    LIKE4_ LIKEC_ between | Member of multiset SUBMULTISET_
    The symbol ',' was replaced by 'AUDIT_COLUMN_OPTS' continue.


    SQL >
    SQL > start
    (2 dbms_fga.add_policy)
    3 object_schema = > "SA."
    object_name 4 = > "TABLE_CASE"
    5 policy_name = > "SA_Audit"
    6 audit_condition = > 'status = "A" '.
    7 audit_column = > 'OBJID, S_TITLE, CASE_STATE2CONDITION. "
    8 handler_schema = > "SA."
    9 handler_module = > "FGA_HANDLER"
    10 activate = > TRUE,
    11 statement_types = > ' SELECT, UPDATE.
    12 audit_trail = > ' DBMS_FGA. SCOPES '.
    13 audit_column_opts = > "all_columns");
    14 end;
    15.
    AUDIT_TRAIL = > ' DBMS_FGA. SCOPES '.
    *
    ERROR on line 12:
    ORA-06550: line 12, column 1:
    PLS-00103: encountered the symbol "AUDIT_TRAIL" when awaits an of the
    Next:
    ), * & = - + <>/ is mod remains not rem
    < an exponent (*) > <>or! = or ~ = > = < = <>and or LIKE2_
    LIKE4_ LIKEC_ between | Member of multiset SUBMULTISET_
    The symbol ',' was replaced by "AUDIT_TRAIL" continue.


    SQL > statement_types = > "SELECT, UPDATE.
    SP2-0734: order unknown beginning «statement_...» "- rest of line is ignored.
    SQL >
    SQL >
    SQL > start
    (2 dbms_fga.add_policy)
    3 object_schema = > "SA."
    object_name 4 = > "TABLE_CASE"
    5 policy_name = > "SA_Audit"
    6 audit_condition = > 'status = "A" '.
    7 audit_column = > 'OBJID, S_TITLE, CASE_STATE2CONDITION. "
    8 handler_schema = > "SA."
    9 handler_module = > "FGA_HANDLER"
    10 activate = > TRUE,
    11 statement_types = > ' SELECT, UPDATE.
    12 audit_column_opts = > "all_columns");
    13 end;
    14.
    audit_column_opts = > "all_columns");
    *
    ERROR on line 12:
    ORA-06550: line 12, column 1:
    PLS-00103: encountered the symbol "AUDIT_COLUMN_OPTS" when awaits an of the
    Next:
    ), * & = - + <>/ is mod remains not rem
    < an exponent (*) > <>or! = or ~ = > = < = <>and or LIKE2_
    LIKE4_ LIKEC_ between | Member of multiset SUBMULTISET_
    The symbol ',' was replaced by 'AUDIT_COLUMN_OPTS' continue.



    Help me please guys, I tried by all means,

    statement_types => ' SELECT, UPDATE.

    You are missing a comma. You need a comma after the STATEMENT_TYPES parameter.

  • Is it possible to read from stack to stack memory function code or not?

    Hi all

    in the case of an error, I'd need to log where the exaclly error occurred for example in which evolve and with what settings (like watching track battery in LabWindows/CVI).

    Does anyone know how to read the stack function names and parameters?

    Best regards

    Milan.

    Hi Milan,

    First of all, you can try looking at this code example that I posted to the community that describes the features that make the error checking, use macros __FILE__, __FUNCTION__ and __LINE__ to inform the user of an error.

    The only way I can think to save the settings of the function errors use variable argument functions: in this case all parameters to the function is accessible via some macros so that inside the function, you can write a line of code to connect each of them in the debug output window or a file or anything you want. You can start the search here, here and here for some references and examples of code. While I've used the variable arguments functions, their use for the scope of error logging is just a conceptual framework: I have not really tried to do, but I guess it can be done this way.

  • Bad system setting, cannot start the database

    Hello, I have problem with start my database

    C:\Users\Raw>sqlplus "/ as sysdba"


SQL*Plus: Release 11.2.0.1.0 Production on Thu May 28 15:23:34 2015


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


Connected to an idle instance.

SQL> startup
ORACLE instance started.


Total System Global Area 1068937216 bytes
Fixed Size                  2182592 bytes
Variable Size             587203136 bytes
Database Buffers          473956352 bytes
Redo Buffers                5595136 bytes
Database mounted.
ORA-01092: ORACLE instance terminated. Disconnection forced
ORA-30012: undo tablespace 'UNDOTS3' does not exist or of wrong type
Process ID: 2716
Session ID: 5 Serial number: 3

SQL> startup mount
ORACLE instance started.


Total System Global Area 1068937216 bytes
Fixed Size                  2182592 bytes
Variable Size             587203136 bytes
Database Buffers          473956352 bytes
Redo Buffers                5595136 bytes
Database mounted.
SQL> show parameter undo


NAME                                 TYPE        VALUE
------------------------------------ ----------- ------------------------------
undo_management                      string      AUTO
undo_retention                       integer     900
undo_tablespace                      string      UNDOTS3
SQL> select * from v$tablespace;


       TS# NAME                           INC BIG FLA ENC
---------- ------------------------------ --- --- --- ---
         0 SYSTEM                         YES NO  YES
         1 SYSAUX                         YES NO  YES
         2 UNDOTBS1                       YES NO  YES
         4 USERS                          YES NO  YES
         3 TEMP                           NO  NO  YES
         6 ARB_TABLESPACE                 YES NO  YES
         7 ARB2_TABLESPACE                YES NO  YES
         5 UNDOTBS2                       YES NO  YES
         8 TEMP2                          NO  NO  YES
         9 UNDOTBS3                       YES NO  YES


10 rows selected.


SQL> alter system set undo_tablespace=UNDOTBS3 scope=both;
alter system set undo_tablespace=UNDOTBS3 scope=both
*
ERROR at line 1:
ORA-02097: parameter cannot be modified because specified value is invalid
ORA-01219: database not open: queries allowed on fixed tables/views only

SQL> alter database open
  2  ;
alter database open
*
ERROR at line 1:
ORA-01092: ORACLE instance terminated. Disconnection forced
ORA-30012: undo tablespace 'UNDOTS3' does not exist or of wrong type
Process ID: 1128
Session ID: 5 Serial number: 3

SQL>

    When I have a parameter not valid, the I often resolve when the database does not open is to simply create a pfile the spfile file:

    sqlplus

    Connect / as sysdba

    create pfile='/home/oracle/pfile.txt 'to spfile='/u01/app/oracle/product/12.1.0.2/dbs/spfileorcl.ora ';

    Then use a text editor to fix the value of the parameter. When done, save the changes. Then create spfile from pfile this and you should be able to start the instance.

    create spfile='/u01/app/oracle/product/12.1.0.2/dbs/spfileorcl.ora 'to pfile='/home/oracle/pfile.txt ';

    startup

    HTH,

    Brian

  • chanege ASM instance parameter

    Help, please

    How to change the instance ASM MEMORY_TARGET parameter?

    SQL > show the spfile parameter

    VALUE OF TYPE NAME
    ------------------------------------ ----------- ------------------------------
    chain of SPFile
    SQL >

    $ asmcmd spget
    +OCR_VOTE/c1se/asmparameterfile/registry.253.812471763

    SQL > alter system set MEMORY_TARGET = 800M scope = both;
    ALTER system set MEMORY_TARGET = 800M scope = both
    *
    ERROR on line 1:
    ORA-32001: write to SPFILE requested but no SPFILE is in use

    How to change the settings for Oracle ASM instance?

    Thank you to

    ASM instance can start without any file parameter. To create the spfile, use:

    SQL > create spfile from memory;

    This will update OCR (or grid profile).

  • Erase (delete) a SPFILE parameter

    11.2.0.3/Solaris

    I want to clear the value set for LOCAL_LISTENER and set the value to null. According to the doc, I have to use the RESET command. But the RESET works that with SCOPE = SPFILE. That is to say. I have to bounce the DB to bring this amendment into force.
    SQL> show parameter spfile

NAME                                 TYPE        VALUE
------------------------------------ ----------- ------------------------------
spfile                               string      /u01/app/oracle/product/11.2.0
                                                 /dbhome_1/dbs/spfileorcl.ora
SQL>
SQL> show parameter LOCAL_LISTENER

NAME                                 TYPE        VALUE
------------------------------------ ----------- ------------------------------
local_listener                       string      (DESCRIPTION=(ADDRESS=(PROTOCO
                                                 L=TCP)(HOST=192.168.0.182)(POR
                                                 T=1892)))
SQL>
SQL>
SQL>
SQL> alter system reset LOCAL_LISTENER scope=both;
alter system reset LOCAL_LISTENER scope=both
*
ERROR at line 1:
ORA-32029: resetting with SCOPE=MEMORY or SCOPE=BOTH is currently not supported


SQL> alter system reset LOCAL_LISTENER ;

System altered.

SQL> show parameter spfile

NAME                                 TYPE        VALUE
------------------------------------ ----------- ------------------------------
spfile                               string      /u01/app/oracle/product/11.2.0
                                                 /dbhome_1/dbs/spfileorcl.ora
SQL>

------ Still showing the old value as a bounce is required
SQL> show parameter LOCAL_LISTENER

NAME                                 TYPE        VALUE
------------------------------------ ----------- ------------------------------
local_listener                       string      (DESCRIPTION=(ADDRESS=(PROTOCO
                                                 L=TCP)(HOST=192.168.0.182)(POR
                                                 T=1892)))
    Is the empty string parameter supported in Oracle. It seems to have worked for me, but I would like to know if it is recommended.
    SQL> show parameter LOCAL_LISTENER

NAME                                 TYPE        VALUE
------------------------------------ ----------- ------------------------------
local_listener                       string      (DESCRIPTION=(ADDRESS=(PROTOCO
                                                 L=TCP)(HOST=192.168.0.182)(POR
                                                 T=1892)))

SQL> alter system set LOCAL_LISTENER = '' scope = both;

System altered.

SQL> show parameter LOCAL_LISTENER

NAME                                 TYPE        VALUE
------------------------------------ ----------- ------------------------------
local_listener                       string
SQL>
    The article says it is not recommended to use an empty string. But, what other choice do I have to clear the value of a parameter without bouncing the DB?
    http://Coskan.WordPress.com/2007/03/07/setting-or-resetting-unsetting-parameters/

    Published by: greeny on November 12, 2012 06:25

    It's how erase editable a SPFILE parameter

    I usually use the following to do this:

    alter system reset  scope=spfile sid='*';

    Reference to the alter_system_reset_clause of the SQL language for more information reference:

    "This clause allows you to remove the frame, for any instance, any initialization parameter in the spfile which was used to start the instance." etc.

  • Need help on DR Failover to production database

    Database: Oracle Database 10 g Enterprise Edition Release 10.2.0.3.0 - 64 bit Production
    Operating system: Solaris
    Type of replication: Dataguard (with brokers)
    Problem:
    Due to the failure of feed on the production we spent our secondary primary security goal allowed us to point of blowback on current production (old reserve), now hopefully we will face the problem during the transition to production, if it please help and guide which will be the best practice in this case and because of the flashback on squnce Exchange not getting out of the Please help this problem and guide

    MAX(SEQUENCE#)
    --------------
    9221

    ========#######================

    Last login: Wednesday, 5 Sep 01:51:32 in the 10.245.13.6
    $ su - oracle
    Password:
    Mesg: cannot change the mode
    $ ps - ef | grep pmon
    2978 1 oratst 0 Sep 08? 233:10 ora_pmon_amantst
    Oracle 3039 1 0 Sep 08? 209:09 ora_pmon_airman
    Oracle 17582 17574 0 05:41:15 pts/1 0:00 grep pmon


    $ sqlplus

    SQL * more: release 10.2.0.3.0 - Production on Sea 5 05:56:21 Sep 2012

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

    Enter the user name: virtue sysdba

    Connected to:
    Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 - 64 bit Production
    With partitioning, OLAP and Data Mining options

    SQL > list of archive logs
    Database log mode Archive Mode
    Active AutoArchive
    Archives/u01/oradata/airman/archive destination
    Sequence of journal online oldest 9220
    Log sequence to archive 0
    Current log sequence 9222
    SQL > exit
    Disconnected from the database to Oracle 10 g Enterprise Edition Release 10.2.0.3.0 - 64 bit Production
    With partitioning, OLAP and Data Mining options

    $ sqlplus

    SQL * more: release 10.2.0.3.0 - Production on Sea 5 05:57:08 Sep 2012

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

    Enter the user name: virtue sysdba

    Connected to:
    Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 - 64 bit Production
    With partitioning, OLAP and Data Mining options

    SQL > show parameter dump

    VALUE OF TYPE NAME
    ------------------------------------ ----------- ------------------------------
    background_core_dump partial string
    the string background_dump_dest/u01/app/oracle/admin/airman/b
    Tipper
    core_dump_dest string/u01/app/oracle/admin/airman/c
    Tipper
    max_dump_file_size string UNLIMITED
    shadow_core_dump partial string
    user_dump_dest string/u01/app/oracle/admin/airman/u
    Tipper
    SQL > exit
    Disconnected from the database to Oracle 10 g Enterprise Edition Release 10.2.0.3.0 - 64 bit Production
    With partitioning, OLAP and Data Mining options
    $ cd/u01/app/oracle/admin/airman/bdump
    alert of $ ls - lrt
    Alert: no such file or directory
    $ *
    ksh: airman_arc0_11192.trc: cannot run
    $ ls - lrt alert *.
    -rw - r - 1 oracle oinstall 5323818 4 September 20:54 alert_airman.log
    flashback $ mkdir
    chmod $755 flashback

    $ sqlplus

    SQL * more: release 10.2.0.3.0 - Production Wed Sep 5 06:10:06 2012

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

    Enter the user name: virtue sysdba

    Connected to:
    Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 - 64 bit Production
    With partitioning, OLAP and Data Mining options

    SQL > select max(sequence#) from v$ log_history;

    MAX(SEQUENCE#)
    --------------
    9221

    SQL > select NAME, DATABASE_ROLE, GUARD_STATUS, SWITCHOVER_STATUS, switch to THE #, OPEN_MODE, PROTECTION_MODE from v$ database;

    NAME DATABASE_ROLE GUARD_S SWITCHOVER_STATUS PASSAGE TO THE # OPEN_MODE
    --------- ---------------- ------- -------------------- ----------- ----------
    PROTECTION_MODE
    --------------------
    AIRMAN PHYSICAL STANDBY NO SESSIONS ACTIVE 4176335025 MOUNTED
    MAXIMUM PERFORMANCE


    SQL > select NAME, DATABASE_ROLE, GUARD_STATUS from v$ database;

    NAME DATABASE_ROLE GUARD_S
    --------- ---------------- -------
    AIRMAN PHYSICAL STANDBY NO

    SQL > select SWITCHOVER_STATUS, passage to THE #, OPEN_MODE, PROTECTION_MODE from v$ database;

    SWITCHOVER_STATUS PASSAGE TO THE # OPEN_MODE PROTECTION_MODE
    -------------------- ----------- ---------- --------------------
    SESSIONS ACTIVE 4176335025 MOUNTED A MAXIMUM PERFORMANCE

    ==================================================

    Enter the user name: virtue sysdba

    Connected to:
    Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 - 64 bit Production
    With partitioning, OLAP and Data Mining options

    SQL > select name, open_mode from v$ database;

    NAME OPEN_MODE
    --------- ----------
    AVIATOR MOUNTED

    SQL > show parameter log_archive_dest_

    VALUE OF TYPE NAME
    ------------------------------------ ----------- ------------------------------
    Log_archive_dest_1 LOCATION string = / u01/oradata/Aviator/a
    rchive VALID_FOR (ALL_LOGFILES =
    ALL_ROLES) db_unique_name = air
    man_sj
    LOG_ARCHIVE_DEST_10 string
    chain of LOG_ARCHIVE_DEST_2 SERVICE = airman_kj LGWR ASYNC V
    ALID_FOR = (ONLINE_LOGFILE, PRIMA)
    RY_ROLE) db_unique_name = Aviator
    _kj
    log_archive_dest_3 string
    log_archive_dest_4 string

    VALUE OF TYPE NAME
    ------------------------------------ ----------- ------------------------------
    log_archive_dest_5 string
    log_archive_dest_6 string
    log_archive_dest_7 string
    log_archive_dest_8 string
    log_archive_dest_9 string
    allow the chain of log_archive_dest_state_1
    allow the chain of log_archive_dest_state_10
    allow the chain of LOG_ARCHIVE_DEST_STATE_2
    allow the chain of log_archive_dest_state_3
    allow the chain of log_archive_dest_state_4
    allow the chain of log_archive_dest_state_5

    VALUE OF TYPE NAME
    ------------------------------------ ----------- ------------------------------
    allow the chain of log_archive_dest_state_6
    allow the chain of log_archive_dest_state_7
    allow the chain of log_archive_dest_state_8
    allow the chain of log_archive_dest_state_9
    SQL >
    SQL > alter system set log_archive_dest_2 = delay;
    ALTER system set log_archive_dest_2 = reporter
    *
    ERROR on line 1:
    ORA-02097: the parameter cannot be changed because specified value is not valid
    ORA-16024: parameter LOG_ARCHIVE_DEST_2 cannot be parsed.


    SQL > alter system set log_archive_dest_2 = reporter scope = mΘmoire;
    ALTER system set log_archive_dest_2 = scope reporter = mΘmoire
    *
    ERROR on line 1:
    ORA-02097: the parameter cannot be changed because specified value is not valid
    ORA-16024: parameter LOG_ARCHIVE_DEST_2 cannot be parsed.


    SQL > alter system set log_archive_dest_2 = reporter scope = both;
    ALTER system set log_archive_dest_2 = reporter scope = both
    *
    ERROR on line 1:
    ORA-32001: write requested SPFILE but no SPFILE specified at startup


    SQL > show the spfile parameter

    VALUE OF TYPE NAME
    ------------------------------------ ----------- ------------------------------
    chain of SPFile


    $ sqlplus

    SQL * more: release 10.2.0.3.0 - Production Wed Sep 5 06:26:40 2012

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

    Enter the user name: virtue sysdba

    Connected to:
    Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 - 64 bit Production
    With partitioning, OLAP and Data Mining options

    SQL > select name, open_mode from v$ database;

    NAME OPEN_MODE
    --------- ----------
    AVIATOR MOUNTED

    SQL > create spfile from pfile;

    Created file.

    SQL > alter database recover managed standby database cancel;

    Database altered.

    SQL > show parameter dump

    VALUE OF TYPE NAME
    ------------------------------------ ----------- ------------------------------
    background_core_dump partial string
    the string background_dump_dest/u01/app/oracle/admin/airman/b
    Tipper
    core_dump_dest string/u01/app/oracle/admin/airman/c
    Tipper
    max_dump_file_size string UNLIMITED
    shadow_core_dump partial string
    user_dump_dest string/u01/app/oracle/admin/airman/u
    Tipper
    SQL > shutdown immediate;
    ORA-01109: database is not open


    The database is dismounted.
    ORACLE instance stops.
    SQL > startup nomount
    ORACLE instance started.

    Total System Global Area 209715200 bytes
    Bytes of size 2029008 fixed
    150997552 variable size bytes
    54525952 of database buffers bytes
    Redo buffers 2162688 bytes
    SQL > show the spfile parameter

    VALUE OF TYPE NAME
    ------------------------------------ ----------- ------------------------------
    /U01/app/Oracle/product/10.2.0 string SPFile
    /Db_1/DBS/spfileairman.ora
    SQL > alter database base_de_donnees eve of Mount;

    Database altered.

    SQL > ALTER DATABASE RECOVER MANAGED STANDBY BASE DISCONNECT FROM the SESSION.

    Database altered.

    SQL > show parameter log_archive_dest_

    VALUE OF TYPE NAME
    ------------------------------------ ----------- ------------------------------
    Log_archive_dest_1 LOCATION string = / u01/oradata/Aviator/a
    rchive VALID_FOR (ALL_LOGFILES =
    ALL_ROLES) db_unique_name = air
    man_sj
    LOG_ARCHIVE_DEST_10 string
    chain of LOG_ARCHIVE_DEST_2 SERVICE = airman_kj LGWR ASYNC V
    ALID_FOR = (ONLINE_LOGFILE, PRIMA)
    RY_ROLE) db_unique_name = Aviator
    _kj
    log_archive_dest_3 string
    log_archive_dest_4 string

    VALUE OF TYPE NAME
    ------------------------------------ ----------- ------------------------------
    log_archive_dest_5 string
    log_archive_dest_6 string
    log_archive_dest_7 string
    log_archive_dest_8 string
    log_archive_dest_9 string
    allow the chain of log_archive_dest_state_1
    allow the chain of log_archive_dest_state_10
    allow the chain of LOG_ARCHIVE_DEST_STATE_2
    allow the chain of log_archive_dest_state_3
    allow the chain of log_archive_dest_state_4
    allow the chain of log_archive_dest_state_5

    VALUE OF TYPE NAME
    ------------------------------------ ----------- ------------------------------
    allow the chain of log_archive_dest_state_6
    allow the chain of log_archive_dest_state_7
    allow the chain of log_archive_dest_state_8
    allow the chain of log_archive_dest_state_9
    SQL > alter system set log_archive_dest_2 = reporter scope = both;
    ALTER system set log_archive_dest_2 = reporter scope = both
    *
    ERROR on line 1:
    ORA-32017: failure of updated SPFILE
    ORA-16179: progressive changes to 'log_archive_dest_2' unauthorized with SPFILE


    SQL > alter system set log_archive_dest_2 = reporter scope = mΘmoire;
    ALTER system set log_archive_dest_2 = scope reporter = mΘmoire
    *
    ERROR on line 1:
    ORA-02097: the parameter cannot be changed because specified value is not valid
    ORA-16024: parameter LOG_ARCHIVE_DEST_2 cannot be parsed.


    SQL > alter system set log_archive_dest_state_2 = reporter scope = both;

    Modified system.

    SQL > show parameter log_archive_dest_state_2

    VALUE OF TYPE NAME
    ------------------------------------ ----------- ------------------------------
    LOG_ARCHIVE_DEST_STATE_2 string DAVID
    SQL > show parameter db_recovery_file_dest

    VALUE OF TYPE NAME
    ------------------------------------ ----------- ------------------------------
    db_recovery_file_dest string
    db_recovery_file_dest_size large integer 0
    SQL > alter system set db_recovery_file_dest = ' / u01/oradata/flashback. "
    ALTER system set db_recovery_file_dest = ' / u01/oradata/flashback.
    *
    ERROR on line 1:
    ORA-02097: the parameter cannot be changed because specified value is not valid
    ORA-19802: cannot use DB_RECOVERY_FILE_DEST, DB_RECOVERY_FILE_DEST_SIZE without


    SQL > alter system set db_recovery_file_dest_size = 14G;

    Modified system.

    SQL > alter system set db_recovery_file_dest = ' / u01/oradata/flashback. "

    Modified system.

    SQL > show parameter db_recovery_file_dest

    VALUE OF TYPE NAME
    ------------------------------------ ----------- ------------------------------
    db_recovery_file_dest string/u01/oradata/flashback
    whole large db_recovery_file_dest_size 14G
    SQL > show parameter db_flashback_retention_target

    VALUE OF TYPE NAME
    ------------------------------------ ----------- ------------------------------
    db_flashback_retention_target around 1440
    SQL > alter system set db_flashback_retention_target = 2880;

    Modified system.

    SQL > create spfile from pfile;

    Created file.

    SQL > alter database recover managed standby database cancel;

    Database altered.

    SQL > alter flashback database;

    Database altered.

    SQL > create restore point guaranteed before_open_standby flashback database;

    Restore point created.

    SQL > select Yvert, storage_size, time, name from v$ restore_point;

    RCS STORAGE_SIZE
    ---------- ------------
    TIME
    ---------------------------------------------------------------------------
    NAME
    --------------------------------------------------------------------------------
    1536320779 8192000
    06.37.50.000000000 05-AUG-12 AM
    BEFORE_OPEN_STANDBY


    SQL > set linesize 200
    SQL > col Yvert, storage_size, time, name format a25
    SQL > select Yvert, storage_size, time, name from v$ restore_point;

    SNA STORAGE_SIZE TIMES
    ---------- ------------ ---------------------------------------------------------------------------
    NAME
    --------------------------------------------------------------------------------------------------------------------------------
    1536320779 8192000 05-AUG-12 AM 06.37.50.000000000
    BEFORE_OPEN_STANDBY


    SQL > alter database activate standby database;

    Database altered.

    SQL > select database_role from database v$.

    DATABASE_ROLE
    ----------------
    PRIMARY

    SQL > shutdown immediate;
    ORA-01109: database is not open


    The database is dismounted.
    ORACLE instance stops.
    SQL > startup
    ORACLE instance started.

    Total System Global Area 209715200 bytes
    Bytes of size 2029008 fixed
    150997552 variable size bytes
    54525952 of database buffers bytes
    Redo buffers 2162688 bytes
    Mounted database.
    Open database.
    SQL > select name, open_mode from v$ database;

    NAME OPEN_MODE
    --------- ----------
    AIRMAN READING WRITING

    SQL > select max(sequence#) from v$ log_history;

    MAX(SEQUENCE#)
    --------------
    9221

    Published by: NATALIE on September 7, 2012 09:31

    Salvation;

    "" I suggest you close your question here as has answered your question move Home Forum ' high availability ' Dataguard which is dedicated Dataguard forum site.

    Respect of
    HELIOS

  • How can I set _gby_hash_aggregation_enabled = FALSE in 11 GR 2

    Hello
    I am tiring to define together gbyhash_aggregation_enabled = FALSE in my new 11 GR 2 instance using the:

    ALTER system set gbyhash_aggregation_enabled is false scope = spfile;.

    And I get this:

    ALTER system set gbyhash_aggregation_enabled = false scope = spfile
    *
    ERROR on line 1:
    ORA-00911: invalid character

    change the system '_gby_hash_aggregation_enabled' = false;

  • All parameter RECYCLEBIN.

    Hello

    ORACLE: 11 GR 2
    OS: Fedora 14

    Book's RECYCLEBIN synamic initialization parameter. If you can change it using
    SQL > alter system set recyclebin = off scope = both;




    But when I do that, I get the error like...
    ----------
    SQL > alter system set recyclebin = off scope = mΘmoire;
    change system recyclebin set = off scope = mΘmoire
    *
    ERROR on line 1:
    ORA-02096: specified initialization parameter is not editable with this
    option
    ---------
    SQL > alter system set recyclebin = off scope = both;
    change system recyclebin set = off scope = both
    *
    ERROR on line 1:
    ORA-02096: specified initialization parameter is not editable with this
    option
    ---------


    But when I run as follows
    ------------
    SQL > alter system set recyclebin = off scope = spfile;

    Modified system.
    ---------


    Can someone please tell me why I might be faced with problems when you perform the scop = memory and scope = both. When it comes to a dynamic parameter.

    With thanks...
    Nishya...

    Published by: 937499 on May 30, 2012 12:45 AM

    Book's RECYCLEBIN synamic initialization parameter.

    What book?

    You could (and should) have looked through a quick and simple search @ http://www.oracle.com/pls/db112/homepage

    "Enable you and disable the Recycle Bin by changing the recyclebin initialization parameter. * This setting is not dynamic, so a restart of the database is required when change you it with an ALTER SYSTEM statement *. »
    http://docs.Oracle.com/CD/E11882_01/server.112/e25494/tables011.htm#ADMIN11680

    Published by: Hoek on May 30, 2012 09:57

  • LOG_ARCHIVE_DEST_STATE_n = REPORTER

    Version: 11.2
    OPERATING SYSTEM: AIX 6.1

    It's my understanding of the LOG_ARCHIVE_DEST_n parameter
    LOG_ARCHIVE_DEST_1 is the destination of the archive primary
    LOG_ARCHIVE_DEST_2 specifies the location where the archive logs should be sent and what process (LGWR or ARCr) must be used to transport it again for the rescue site
    LOG_ARCHIVE_DEST_1='LOCATION=/u01/app/oracle/oradata/white/arch/ VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=white'
LOG_ARCHIVE_DEST_2='SERVICE=black LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=black'
    My question is about LOG_ARCHIVE_DEST_STATE_n which is normally set to ACTIVATE. I would like to know under what circumstances do we set one of these parameters to DEFER
    LOG_ARCHIVE_DEST_STATE_1=DEFER
LOG_ARCHIVE_DEST_STATE_2=DEFER

    My question is about LOG_ARCHIVE_DEST_STATE_n which is normally set to ACTIVATE. I would like to know under what circumstances do we set one of these parameters to DEFER

    You should have local LOG_ARCHIVE_DEST/LOG_ARCHIVE_DEST_1 need to be activated because its archives in view log.

    "When database is in ARCHIVE LOG MODE"
sys@ORCL> alter system set log_archive_dest_state_1='defer' scope=both;
alter system set log_archive_dest_state_1='defer' scope=both
*
ERROR at line 1:
ORA-02097: parameter cannot be modified because specified value is invalid
ORA-16028: new LOG_ARCHIVE_DEST_STATE_1 causes less destinations than LOG_ARCHIVE_MIN_SUCCEED_DEST
requires
sys@ORCL>

"Now Database im putting in NOARCHIVELOG Mode" 

sys@ORCL> shut immediate
Database closed.
Database dismounted.
ORACLE instance shut down.
sys@ORCL> startup mount
ORACLE instance started.

Total System Global Area  770035712 bytes
Fixed Size                  1377304 bytes
Variable Size             356518888 bytes
Database Buffers          406847488 bytes
Redo Buffers                5292032 bytes
Database mounted.
sys@ORCL> alter database noarchivelog;

Database altered.

sys@ORCL> alter database open;

Database altered.

sys@ORCL> archive log list
Database log mode              No Archive Mode
Automatic archival             Disabled
Archive destination            c:\oracle\flash_recovery_area
Oldest online log sequence     23
Current log sequence           25
sys@ORCL> alter system set log_archive_dest_state_1='defer' scope=both;

System altered.

sys@ORCL>

"When noarchivelog mode you should able to disable local destination"

    Now lets discuss about remote destinations, i.e.: LOG_ARCHIVE_DEST_2

    When you set this parameter, then sending archive/redo will be stopped to remote destinations.
    In the case of a failover of backup database (or) If make you patches (or) such maintenance you may need to disable the settings.

    Hope this clears.

    Published by: CKPT on March 22, 2012 09:27

  • SQL command to define shared_pool_size

    Dear Guru:

    What is the sql command to define shared_pool_size = 400 MB

    I try SQL command below, but not work
    change the system shared_pool_size set = 400 M scope = both;

    error = > ORA-02097 parameter is not editable because specified value is not valid.
    ORA-04033 memory to push the pool.



    Thanks in advance.

    user11403781 wrote:
    Dear Guru:

    What is the sql command to define shared_pool_size = 400 MB

    I try SQL command below, but not work
    change the system shared_pool_size set = 400 M scope = both;

    error-online ORA-02097 parameter is not editable because specified value is not valid.
    ORA-04033 memory to push the pool.

    Thanks in advance.

    change the system shared_pool_size set = 400 M scope = spfile;

Maybe you are looking for