Oracle Designer pre 6i to 6i igration sql to get tablespace data

ok now I want sql to find the tables space definitions in use for the latest version of the tables? ?
pre 6i version
select lower(ti.GLOBAL_SYNONYM_NAME)||'*'||ts.name
from
ci_application_systems a, ci_table_implementations ti, ci_tablespaces ts, ci_storage_definitions sd
where
ts.ID = ti.TABLESPACE_REFERENCE and
sd.ID = ti.STORAGE_DEFINITION_REFERENCE and
a.APPLICATION_SYSTEM_OWNER = '&OWNER' and
a.NAME = &APPand
ti.GLOBAL_SYNONYM_NAME IS NOT NULL
order by ti.GLOBAL_SYNONYM_NAME asc;
any ideas on what the 6i version should be ?

If you don't already know this, here's a tip:
In the Design Editor (DE) go to the DB Admin tab then navigate to:
Oracle Databases > Users > Schema Objects > Table Implementations
Open the properties palette for a table definition
In the Properties select 'Storage Definition' then press your keyboard 'F5' key.
It displays various internal details about a selected property and the element to which it relates. That should help you work out what you need to query.
You can also use F5 in other tools, e.g. the RON

Similar Messages

  • Sql to get monthwise data

    Hi experts,
    I have a query to get data monthwise for a particular column value from this table
    SQL> desc doctor_patient_diagnosis_tab
    Name Null? Type
    DOCTOR_CODE VARCHAR2(8)
    VISIT_ID NUMBER(12)
    DIAGNOSIS VARCHAR2(2000)
    EMP_NO NUMBER(6)
    TRANSACTION_DATE DATE
    FINAL_TAG VARCHAR2(1)
    DIAGNOSIS_CODE VARCHAR2(8)
    in the following way to display......
    Diagnosis Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec Total
    OTHER DISEASES 15 4 5 9 14 31 8 1 6 7 2 5 107
    ROUTINE DEWORMING 14 4 7 7 9 3 9 9 2 4 9 14 91
    my query is as follows.... but not giving me exact result
    select substr(diagnosis,1,20) diag,
    count(decode(TO_CHAR(transaction_date,'MON'),'JAN',VISIT_ID,0)) jan,
    count(decode(TO_CHAR(transaction_date,'MON'),'FEB',VISIT_ID,0)) feb,
    count(decode(TO_CHAR(transaction_date,'MON'),'MAR',VISIT_ID,0)) mar,
    count(decode(TO_CHAR(transaction_date,'MON'),'APR',VISIT_ID,0)) apr,
    count(decode(TO_CHAR(transaction_date,'MON'),'MAY',VISIT_ID,0)) may,
    count(decode(TO_CHAR(transaction_date,'MON'),'JUN',VISIT_ID,0)) jun,
    count(decode(TO_CHAR(transaction_date,'MON'),'JUL',VISIT_ID,0)) jul,
    count(decode(TO_CHAR(transaction_date,'MON'),'AUG',VISIT_ID,0)) aug,
    count(decode(TO_CHAR(transaction_date,'MON'),'SEP',VISIT_ID,0)) sep,
    count(decode(TO_CHAR(transaction_date,'MON'),'OCT',VISIT_ID,0)) oct,
    count(decode(TO_CHAR(transaction_date,'MON'),'NOV',VISIT_ID,0)) nov,
    count(decode(TO_CHAR(transaction_date,'MON'),'DEC',VISIT_ID,0)) dec
    from doctor_patient_diagnosis_tab
    WHERE to_char(transaction_date,'DD-MON-YYYY') >='01-JAN-2011'
    GROUP BY diagnosis
    ORDER BY 1;
    can someone assist me in this ...
    Thank you

    Hi kiran,
    It is helpful for me but not yet achieved the result, when I run the inner query it gives as.....
    SQL> select substr(diagnosis,1,20) diag,
    2 decode(TO_CHAR(transaction_date,'MON'),'JAN',VISIT_ID,0) jan,
    3 decode(TO_CHAR(transaction_date,'MON.'),'FEB',VISIT_ID,0) feb,
    4 decode(TO_CHAR(transaction_date,'MON'),'MAR',VISIT_ID,0) mar,
    5 decode(TO_CHAR(transaction_date,'MON'),'APR',VISIT_ID,0) apr,
    6 decode(TO_CHAR(transaction_date,'MON'),'MAY',VISIT_ID,0) may,
    7 decode(TO_CHAR(transaction_date,'MON'),'JUN',VISIT_ID,0) jun,
    8 decode(TO_CHAR(transaction_date,'MON'),'JUL',VISIT_ID,0) jul,
    9 decode(TO_CHAR(transaction_date,'MON'),'AUG',VISIT_ID,0) aug,
    10 decode(TO_CHAR(transaction_date,'MON'),'SEP',VISIT_ID,0) sep,
    11 decode(TO_CHAR(transaction_date,'MON'),'OCT',VISIT_ID,0) oct,
    12 decode(TO_CHAR(transaction_date,'MON'),'NOV',VISIT_ID,0) nov,
    13 decode(TO_CHAR(transaction_date,'MON'),'DEC',VISIT_ID,0)dec
    14 from doctor_patient_diagnosis_tab
    15 WHERE transaction_date >=to_date('01-JAN-2011','dd-mon-yyyy');
    DIAG JAN FEB MAR APR MAY
    JUN JUL AUG SEP OCT NOV DEC
    AMOEBIASIS 0 0 0 0 0
    3247 0 0 0 0 0 0
    test 200 0 0 0 0
    0 0 0 0 0 0 0
    AMOEBIASIS 0 0 0 0 0
    0 3414 0 0 0 0 0
    DIAG JAN FEB MAR APR MAY
    JUN JUL AUG SEP OCT NOV DEC
    AMOEBIASIS 0 0 0 0 0
    3359 0 0 0 0 0 0
    so one diag comes three times instead of in a single record.
    thanks

  • SQL Help getting Max() date....

    Hi gurus, Here is my situation:
    Here is the sample data:
    Policy_Id Policy-Exp_Dt COl_1
    123_____10/30/2008 __ 333
    123_____ 09/25/2008___445
    123_____ 08/30/2008___443
    Here i have to get the Policy-Exp_Dt from the second row; In other words for all rows which have a similar Policy_Id i should first find out the max(Policy-Exp_Dt) and get the next smallest available date to that.
    I have tried using
    select Policy_Id, COl_1, Policy_Exp_Dt from
    table_1
    where Policy-Exp_Dt = (select max(Policy-Exp_Dt)-1 from
    table_1 a
    where a.policy_id = table_1.policy_id)
    but here i am getting the value = 10/30/2008 - 1 which is 10/29/2008 but i need the value 9/25/2008 which is the next available date less than the max() date.
    Please Advise.
    Edited by: user521009 on Jan 9, 2009 1:56 PM

    I thought to use lag - maybe not as appropriate a ranking functions.
    Also we have a case where there is only One record for a policy - exclude this I guess!
    drop table Max_but_One;
    create table Max_but_One
      Policy_Id      integer      not null,
      Policy_Expires date         not null,
      Policy_Note    varchar2(20) not null
    -- Standard data
    insert into Max_but_One values (123, to_date('30-08-2008','dd-mm-yyyy'), 'First note');
    insert into Max_but_One values (123, to_date('25-09-2008','dd-mm-yyyy'), 'Second note');
    insert into Max_but_One values (123, to_date('30-10-2008','dd-mm-yyyy'), 'Third note');
    -- Standard data again for double check
    insert into Max_but_One values (223, to_date('01-11-2008','dd-mm-yyyy'), 'First note');
    insert into Max_but_One values (223, to_date('02-11-2008','dd-mm-yyyy'), 'Second note');
    -- Only one record for a policy!
    insert into Max_but_One values (323, to_date('01-12-2008','dd-mm-yyyy'), 'First note');
    -- Two or more records for a policy both having the same date which is prior to the max
    insert into Max_but_One values (423, to_date('10-12-2008','dd-mm-yyyy'), 'First note');
    insert into Max_but_One values (423, to_date('10-12-2008','dd-mm-yyyy'), 'Second note');
    insert into Max_but_One values (423, to_date('11-12-2008','dd-mm-yyyy'), 'Third note');
    break on Policy_ID
    select Policy_Id, Policy_Expires, Policy_Note
      from Max_but_One
    order by Policy_Id, Policy_Expires
    POLICY_ID POLICY_EX POLICY_NOTE
           123 30-AUG-08 First note
               25-SEP-08 Second note
               30-OCT-08 Third note
           223 01-NOV-08 First note
               02-NOV-08 Second note
           323 01-DEC-08 First note
           423 10-DEC-08 First note
               10-DEC-08 Second note
               11-DEC-08 Third note
    -- Max Policy_Expires
    select t.*
      from (select Policy_Id, Policy_Expires, Policy_Note
                  ,max(Policy_Expires) over (partition by Policy_Id) as Max_Policy_Expires
              from Max_but_One
           ) t
    where t.Policy_Expires = t.Max_Policy_Expires
    POLICY_ID POLICY_EX POLICY_NOTE          MAX_POLIC
           123 30-OCT-08 Third note           30-OCT-08
           223 02-NOV-08 Second note          02-NOV-08
           323 01-DEC-08 First note           01-DEC-08
           423 11-DEC-08 Third note           11-DEC-08
    -- Using LAG
    select t.Policy_Id
          ,t.Prior_Policy_Expires as Policy_Expires
          ,t.Prior_Policy_Note    as Policy_Note
      from (select Policy_Id, Policy_Expires, Policy_Note
                  ,max(Policy_Expires) over (partition by Policy_Id) as Max_Policy_Expires
                ,lag(Policy_Expires) over (partition by Policy_Id order by Policy_Expires) as Prior_Policy_Expires
                  ,lag(Policy_Note)    over (partition by Policy_Id order by Policy_Expires) as Prior_Policy_Note
              from Max_but_One
           ) t
    where t.Policy_Expires = t.Max_Policy_Expires
    POLICY_ID POLICY_EX POLICY_NOTE
           123 25-SEP-08 Second note
           223 01-NOV-08 First note
           323
           423 10-DEC-08 Second note
    -- To exclude the single record policy then add and t.Prior_Policy_Expires is not null
    select t.Policy_Id
          ,t.Prior_Policy_Expires as Policy_Expires
          ,t.Prior_Policy_Note    as Policy_Note
      from (select Policy_Id, Policy_Expires, Policy_Note
                  ,max(Policy_Expires) over (partition by Policy_Id) as Max_Policy_Expires
                ,lag(Policy_Expires) over (partition by Policy_Id order by Policy_Expires) as Prior_Policy_Expires
                  ,lag(Policy_Note)    over (partition by Policy_Id order by Policy_Expires) as Prior_Policy_Note
              from Max_but_One
           ) t
    where t.Policy_Expires = t.Max_Policy_Expires
       and t.Prior_Policy_Expires is not null
    POLICY_ID POLICY_EX POLICY_NOTE
           123 25-SEP-08 Second note
           223 01-NOV-08 First note
           423 10-DEC-08 Second note
    -- 423 is randomly picked here - could equally have got {423, 10-DEC-08, First note}

  • Oracle designer 6i. Info about the current schema. Can't get tablespace inf

    Oracle designer 6i. I am running sql against the views to get info about the current schema.
    I can't get the tablespace names for the tables used in the latest version of a schema.
    eg the below sql return far too many rows.
    select distinct (lower(ti.GLOBAL_SYNONYM_NAME)||'*'||ts.name )
    from
    ci_application_systems app,
    ci_table_implementations ti,
    ci_tablespaces ts,
    ci_storage_definitions sd
    ,sdd_folder_members mem      
    ,ci_table_definitions td
    where
         app.OWNING_USER = '$OWNER' and
         app.NAME = '$APP_NAME''' and
    app.ivid = (select MAX(ivid) from ci_application_systems app2 where app2.name = '$APP_NAME'') and
    mem.PARENT_IVID = app.IVID and
    mem.MEMBER_OBJECT = td.ID
    and ti.GLOBAL_SYNONYM_NAME IS NOT NULL
         and ti.STORAGE_DEFINITION_REFERENCE = ts.STORAGE_DEFINITION_REFERENCE
    and ts.STORAGE_DEFINITION_REFERENCE = sd.ID

    Hi Neil,
    Thanks for your suggestion. I thought I tried all combinations of database, catalog and schema names and all different orders to connect, associate the connection and generate entities, but it seems I did not try this one. I did exactly what you suggest, except for the fact that I connected to the database before associating the connection to the project.
    It partially works now. I can generate Entities. Once I have generated an entity, all generated private member variables become red underlined, because table "null" for columns "xyz" could not be resolved. And the drop down box for columns in the JPA Details pane still doesn't get populated. The latter can be fixed by selecting the proper schema for the entity, which results in a @Table(schema="xyz") annotation. However, I expected this to be done automatically when the Entity was generated.
    The error about not being able to resolve the columns still exists. I tried to add a @Column(name="ASDF") annotation (because the columns names are all capital, while the member variables are lowercase), but that doesn't resolve the problem.
    I hope this gives you a clue to solve the problem!
    Bart

  • How to get a date range in JDBC sql

    I am using the following in my sql to get a date range... but what if the field is a timestamp will that still work or not...
    AND a.date>=? AND a.date<=?

    Suzie,
    No offence, but is there something stopping you from testing it yourself?
    Good Luck,
    Avi.

  • CDS-11025 Error: Oracle Designer generation error with PL/SQL package

    Hi friends,
    We tried to generate a database package from Oracle Designer (10.1.2.6) and getting "syntax errors" but the package has no syntax errors when we copy and paste the code and compile in TOAD (10.6)
    Error from Designer:
    Server Generator 10.1.2.6 (Build 10.1.2.11.12) , Wed Oct 17 10:58:43 2012
    Copyright (c) Oracle Corporation 1995, 2010. All rights reserved.
    CDS-11025 Error: The PL/SQL within PACKAGE BODY AVP_WATER_ANALYSIS_V has syntax errors - At token 'END', around:
    ...te_dist.VLV_INTL_ID;
    END LOOP;
    Processing Complete: 1 error(s), 0 warning(s)
    code snippet from the Error message:
    FOR rec_update_dist IN cur_update_dist (i_anlyd_intl_id,
    i_iterd_intl_id,
    i_phsed_intl_id,
    i_wtrc_intl_id)
    LOOP
    UPDATE AVP_VALVE AvpValve
    SET AvpValve.DIST_FROM_EDGE = rec_update_dist.DIST_FROM_EDGE
    WHERE AvpValve.ANLYD_INTL_ID = rec_update_dist.ANLYD_INTL_ID
    AND AvpValve.ITERD_INTL_ID = rec_update_dist.ITERD_INTL_ID
    AND AvpValve.PHSED_INTL_ID = rec_update_dist.PHSED_INTL_ID
    AND AvpValve.WTRC_INTL_ID = rec_update_dist.WTRC_INTL_ID
    AND AvpValve.VLV_INTL_ID = rec_update_dist.VLV_INTL_ID;
    END LOOP;
    Thanks for any feedback,
    Jim

    Found the problem.
    It was an issue with the CURSOR with the SELECT ... FROM (SELECT CASE WHEN THEN ELSE END). After swithing to the DECODE statement, Designer is able to generate the package.
    CASE
    WHEN ISOLATION_IND = 'Y' THEN
    'A'
    WHEN OPERATED_IND = 'Y' THEN
    'B'
    ELSE
    'C'
    END
    decode(ISOLATION_IND,'Y','A',decode(OPERATED_IND,'Y','B','C'))
    However, still strange to me that Designer doesn't like the CASE as part of SELECT.
    Edited by: user476620 on Oct 18, 2012 8:13 PM

  • Oracle Designer to SQL Data Modeller Migration

    Hi
    We would like to migrate our artifacts from Oracle Designer to SQL Data Modeller
    Does anybody here have experience with that and things that i should be aware of that is possible with Designer but need to be handled differently in Modeller.

    You might want to try this forum as well: SQL Developer

  • Possibility to register Pre-/Post-Procedures for an SQL Template Handler

    I would appreciate to see the possibility to register pre-/post-procedures for an SQL template handler in ORDS 3.0.
    Why:
    We use Oracle VPD/Row-Level-Security to secure data access. Hence a trigger sets a couple of attributes in the database session context at login time which are then used in static RLS predicates to limit which records the user can see/modify.
    With ORDS 3.0 all sessions are opened under the same technical user (e.g. APEX_REST_PUBLIC_USER), hence all users have the same/no attributes in the session context and could see/modify all data.
    To avoid this situation, I need to set the attributes (e.g. the authenticated user) in the database session context before the actual query/plsql handler is executed.
    Also, resetting the session context after the handler is executed would be good.
    This scenario is in line with scenarios 'One Big Application User' and 'Web-based applications' in http://docs.oracle.com/cd/B28359_01/network.111/b28531/vpd.htm#DBSEG98291.
    Different solution approach:
    Kris suggested to write a PL/SQL handler where the pre-procedure is called before the business logic procedure/query. This is ok for me as long as I modify data and only need to return no or little data.
    As soon as I need to return a lot of data (e.g. select c1, c19, c30 from t1), this approach will force me to write a lot of code in the PL/SQL handler in order to marshal the c1, c19 and c30 to JSON and put it in the HTTP response.
    But this is the beauty of ORDS - I can simply define a template, write a GET SQL Handler 'select c1, c19, c30 from t1'  and have the data available as REST service, without writing any code to write JSON marshaled data in the HTTP response.

    I tried to log the request at Oracle REST Data Services (ORDS) but I could only start a new discussion: Possibility to register Pre-/Post-Procedures for an SQL Template Handler
    As I mentioned there, the PL/SQL handler approach works for me as long as I have no or only little data to send back to the client (e.g. put/post/delete succeeded or an error message why the call failed).
    If I need to return a lot of data from the PL/SQL handler I would need to, as far as I understand, to marshal the data to JSON and write it to the response body in the PL/SQL handler.
    I don't want to do the marshaling, because ORDS does it better.
    However, this works for me:
    I write a pipelined stored procedure that takes as input the attributes I need to set in the session context. I then can reference it in the SQL handler:
    select * from table(my_pipelined_function(:USER, ....)
    Now the JSON/HTTP response is created by ORDS again.
    I still needed to code a couple of lines, but it is way better than duplicating the functionality already existing in ORDS.
    With the hooks it would be perfect because I would not have to write any code (apart from the procedure to set the session context attributes), just configure the REST services in ORDS.

  • Oracle Upgrade --  Pre-Upgrade 10.2.0.4 to 11.2.0.1

    Hello,
    I want to do an Oracle Upgrade to version 11.2g!
    At this point I did some things (in Windows Server 2003 X64):
    1-) Install Oracle 10.2.0.1 (DVD Media);
    2-) Installation of Oracle patchset 10.2.0.4 (note 871735);
    3-) Installation of interim / last generics patch (note 1137346);
    4-) Installation of SAP ECC 6.0 SR3 by SAPInst
    5-) After SAP installation I did all the corrections in Oracle parameters as it mentioned in note 830576.
    As you see above, all the SAP system was well installed!
    But now I want to do the Oracle Upgrade process to the last version, Oracle DB 11.2g  (11.2.0.1)... and so I´m following the Upgrade guide "Upgrade to Oracle Database 11g Release 2 (11.2) Windows.pdf" with some SAP notes for Upgrade process.
    So I´m at this point in planning chapter where is recommended to check so things in actual database, one of this checks are running some SQL-scripts to perform an Oracle database upgrade with DBUA to release 11.2 (as mentioned in note 1431793 - Oracle 11.2.0: Upgrade Scripts)
    I ran two Pre-Scripts, the @pre_upgrade_status.sql and @pre_upgrade_tasks.sql but both outputs showed some warnings and they are worrying me... so what I ask to you is some kind of help in analyse of them and tell me if this issues are relevant for the upgrading process and if so, what you recommend me to do to correct their!
    Next I will post here this two log scripts... they are long!!!

    PRE_UPGRADE_TASKS.log:
    SQL> @pre_upgrade_tasks.sql
    PRE-UPGRADE Tasks: === START ===
    2010-08-05 18:24:13                                                                               
    Recompiling invalid objects
    This reduces the number of invalid objects as much as possible.
    COMP_TIMESTAMP UTLRP_BGN  2010-08-05 18:24:13                                                      
    DOC>   The following PL/SQL block invokes UTL_RECOMP to recompile invalid
    DOC>   objects in the database. Recompilation time is proportional to the
    DOC>   number of invalid objects in the database, so this command may take
    DOC>   a long time to execute on a database with a large number of invalid
    DOC>   objects.
    DOC>
    DOC>   Use the following queries to track recompilation progress:
    DOC>
    DOC>   1. Query returning the number of invalid objects remaining. This
    DOC>       number should decrease with time.
    DOC>          SELECT COUNT(*) FROM obj$ WHERE status IN (4, 5, 6);
    DOC>
    DOC>   2. Query returning the number of objects compiled so far. This number
    DOC>       should increase with time.
    DOC>          SELECT COUNT(*) FROM UTL_RECOMP_COMPILED;
    DOC>
    DOC>   This script automatically chooses serial or parallel recompilation
    DOC>   based on the number of CPUs available (parameter cpu_count) multiplied
    DOC>   by the number of threads per CPU (parameter parallel_threads_per_cpu).
    DOC>   On RAC, this number is added across all RAC nodes.
    DOC>
    DOC>   UTL_RECOMP uses DBMS_SCHEDULER to create jobs for parallel
    DOC>   recompilation. Jobs are created without instance affinity so that they
    DOC>   can migrate across RAC nodes. Use the following queries to verify
    DOC>   whether UTL_RECOMP jobs are being created and run correctly:
    DOC>
    DOC>   1. Query showing jobs created by UTL_RECOMP
    DOC>          SELECT job_name FROM dba_scheduler_jobs
    DOC>          WHERE job_name like 'UTL_RECOMP_SLAVE_%';
    DOC>
    DOC>   2. Query showing UTL_RECOMP jobs that are running
    DOC>          SELECT job_name FROM dba_scheduler_running_jobs
    DOC>          WHERE job_name like 'UTL_RECOMP_SLAVE_%';
    DOC>#
    COMP_TIMESTAMP UTLRP_END  2010-08-05 18:24:15                                                      
    DOC> The following query reports the number of objects that have compiled
    DOC> with errors (objects that compile with errors have status set to 3 in
    DOC> obj$). If the number is higher than expected, please examine the error
    DOC> messages reported with each object (using SHOW ERRORS) to see if they
    DOC> point to system misconfiguration or resource constraints that must be
    DOC> fixed before attempting to recompile these objects.
    DOC>#
                      0                                                                               
    DOC> The following query reports the number of errors caught during
    DOC> recompilation. If this number is non-zero, please query the error
    DOC> messages in the table UTL_RECOMP_ERRORS to see if any of these errors
    DOC> are due to misconfiguration or resource constraints that must be
    DOC> fixed before objects can compile successfully.
    DOC>#
                              0                                                                        
    Purging Recyclebin
    This reduces the time needed for upgrading the database.
    Truncating SYS.AUD$
    This reduces the time needed for upgrading the database.
    Gathering Oracle Dictionary Statistics
    This reduces the time needed for upgrading the database.
    Running Pre-Upgrade-Information Tool utlu112i.sql
    This is a mandatory task for manual database upgrades.
    This tool is also run in pre_upgrade_status.sql.
    Oracle Database 11.2 Pre-Upgrade Information Tool 08-05-2010 18:24:45                              
    Script Version: 11.2.0.1.0 Build: 003                                                              
    Database:                                                                               
    --> name:          PRD                                                                             
    --> version:       10.2.0.4.0                                                                      
    --> compatible:    10.2.0                                                                          
    --> blocksize:     8192                                                                            
    --> platform:      Microsoft Windows x86 64-bit                                                    
    --> timezone file: V4                                                                               
    Tablespaces: [make adjustments in the current environment]                                         
    --> SYSTEM tablespace is adequate for the upgrade.                                                 
    .... minimum required size: 905 MB                                                                 
    --> PSAPUNDO tablespace is adequate for the upgrade.                                               
    .... minimum required size: 84 MB                                                                  
    --> SYSAUX tablespace is adequate for the upgrade.                                                 
    .... minimum required size: 210 MB                                                                 
    --> PSAPTEMP tablespace is adequate for the upgrade.                                               
    .... minimum required size: 61 MB                                                                  
    Flashback: OFF                                                                               
    Update Parameters: [Update Oracle Database 11.2 init.ora or spfile]                                
    Note: Pre-upgrade tool was run on a lower version 64-bit database.                                 
    --> If Target Oracle is 32-Bit, refer here for Update Parameters:                                  
    -- No update parameter changes are required.                                                       
    --> If Target Oracle is 64-Bit, refer here for Update Parameters:                                  
    WARNING: --> "shared_pool_size" needs to be increased to at least 472 MB                           
    Renamed Parameters: [Update Oracle Database 11.2 init.ora or spfile]                               
    -- No renamed parameters found. No changes are required.                                           
    Obsolete/Deprecated Parameters: [Update Oracle Database 11.2 init.ora or spfile]                   
    --> remote_os_authent            11.1       DEPRECATED                                             
    --> background_dump_dest         11.1       DEPRECATED   replaced by  "diagnostic_dest"            
    --> user_dump_dest               11.1       DEPRECATED   replaced by  "diagnostic_dest"            
    Components: [The following database components will be upgraded or installed]                      
    --> Oracle Catalog Views         [upgrade]  VALID                                                  
    --> Oracle Packages and Types    [upgrade]  VALID                                                  
    Miscellaneous Warnings                                                                             
    WARNING: --> Database is using a timezone file older than version 11.                              
    .... After the release migration, it is recommended that DBMS_DST package                          
    .... be used to upgrade the 10.2.0.4.0 database timezone version                                   
    .... to the latest version which comes with the new release.                                       
    Recommendations                                                                               
    Oracle recommends gathering dictionary statistics prior to                                         
    upgrading the database.                                                                            
    To gather dictionary statistics execute the following command                                      
    while connected as SYSDBA:                                                                               
    EXECUTE dbms_stats.gather_dictionary_stats;                                                                               
    Oracle recommends removing all hidden parameters prior to upgrading.                                                                               
    To view existing hidden parameters execute the following command                                   
    while connected AS SYSDBA:                                                                               
    SELECT name,description from SYS.V$PARAMETER WHERE name                                        
            LIKE '\_%' ESCAPE '\'                                                                               
    Changes will need to be made in the init.ora or spfile.                                                                               
    Oracle recommends reviewing any defined events prior to upgrading.                                                                               
    To view existing non-default events execute the following commands                                 
    while connected AS SYSDBA:                                                                         
      Events:                                                                               
    SELECT (translate(value,chr(13)||chr(10),' ')) FROM sys.v$parameter2                           
          WHERE  UPPER(name) ='EVENT' AND  isdefault='FALSE'                                                                               
    Trace Events:                                                                               
    SELECT (translate(value,chr(13)||chr(10),' ')) from sys.v$parameter2                           
          WHERE UPPER(name) = '_TRACE_EVENTS' AND isdefault='FALSE'                                                                               
    Changes will need to be made in the init.ora or spfile.                                                                               
    PRE-UPGRADE Tasks: === FINISHED ===
    SQL> spool off

  • Generation of DDL similar to Oracle Designer (Data Modeler 3.0 EA1.)

    Hi,
    Will the production version of SQL Data Modeler allow the creation of separate DDL files similar to that which Oracle Designer does? For example, I can create a sequence number generator in Data Modeler (DM) and then make a call to that in an Object Type method. However the DDL file that is generated by DM has all DDL in one file. This would allow to take dependencies were taken into consideration, that is create the sequences before object types, packages and tables, then object type bodies, package bodies, etc...
    Thanks,
    ScottK

    At this stage we do not support multiple files. We do plan to do this in the future. However you can work around this by repeating the DDL generation for the different objects types you want to have files for.
    Remember that you can vote on the Exchange for your most desired features.
    Sue

  • Modelling databases in Oracle Designer environment

    Today I had laboratory's which subject was: "Modelling data and designing databases scheme in Oracle Designer environment" and I have to make a report for tommorow. I can't find some answers for questions which our Professor told us to include in the report. I would be very grateful if enyone here can help me.
    1) How looks in SQL code definition of the key of the table if relationship have PRIMARY UID attribute?
    2) Is there any difference in SQL code between references replying to transferable and not transferable relationships
    3) Why some tables have more columns than number of attributes in entities (entities contains the same things that tables)?
    My english isn't perfect, sorry for that. But I hope that I wrote that wuestions correctly.
    Thanks for any help.

    1) a primary UID is a primary key in SQL
    2) No.
    3) OD entity models don't include inherited referential key attributes, whereas the SQL tables (obviously) require them.

  • Oracle Designer 6.0 rel. 2.1.2  hazy installation

    I'm trying to install an oracle designer 6.0 rel 2.1.2.
    I have installed oracle server 8.1.7 on WIN NT workstation
    machine hp p700 128mb. The 8.1.7 server is installed without
    java server because PARAMETER COMPATIBLE = 8.0.5, compatibility
    with 8.0.5 oracle server, needed for designer 6.0 to work ( as
    per docs ).
    I install repository on server then start repository manager on
    client and go create repository. The repository procedure starts
    working then stops at this stage:
    CKRAU20.EXE
    STAGE DETAILS
    CKPACK
    OBJECT DETAILS
    CIOUE_ELEMENT_TYPE
    SUBMITTING DEFINITION/STATEMENT
    CIUEET.OPB
    There's no other way out than killing the process. The problem
    is exactly the ciueet.opb sql package; executed standalone
    against sqlplus, stops everything the same.
    As anybody ever hear about something similar or can guess the
    cause/workaround?
    thank you, daffy duck

    Designer versions prior to version 6.5.40 (aka Designer 6i
    Release 2) will strike this problem when attempting to import or
    install a repository on Oracle database version 8.1.7.
    Patchset 7 for Designer 6.0 has a workaround included so that
    Designer 6.0 can now avoid this problem.
    regards,
    David

  • Oracle Designer 9.0.2.3.

    Hello all,
    I have Oracle Designer 9.0.2.3 installed with an Oracle 9i Database. My repository is created but whenever I eneter any of the Model System Requirements Tools and try to create a new container I get the following messages:
    Message
    ORA-01086: savepoint 'RM_DISPATCH' never established
    Message
    ORA-06512: at line 18
    Message
    ORA-06510: PL/SQL: unhandled user-defined exception
    Message
    RME-02124: Failed to execute SQL statement: declare
    utility varchar2(3);
    curr_el integer;
    begin
    savepoint rm_dispatch;
    rmmes.clear;
    curr_el := 0;
    RMOACTIVITY.OPEN(:p1_el0,:p2_el0);
    :errcnt := 0;
    exception when others then
    rmmes.get_error_state(utility,:excode);
    rmmes.get_product(utility,:exprod);
    :exutil := utility;
    :errcnt := rmmes.getsize;
    :sqlcod := SQLCODE;
    :sqlmsg := SQLERRM;
    :currel := curr_el;
    rollback to savepoint rm_dispatch;
    end;
    Message
    RME-00222: Failed to dispatch operation to Repository
    Message
    RME-00223: Failed to open new activity
    I saw a similar individual have the same type of errors but they were running an older version of Designer. Any help would be appreciated.
    Thanks

    This problem occurs because Oracle9i import and export utilities are not
    compatible with an Oracle 8.1.7 database. This not a bug but an
    Oracle9i design feature.
    Workaround:
    To install Oracle SCM on an Oracle 8.1.7 database, you will first need to
    install Oracle 8.1.7 import and export utilities in a separate Oracle
    Home. The registry variables EXECUTE_IMPORT and EXECUTE_EXPORT need to be
    changed to point to these 8.1.7 import and export
    utilities instead of to the Oracle9i versions. These variables are found under
    the key:
    HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\REPOS61
    Note that when installing the 8.1.7 import and export utilities, the following
    error may be encountered:
    There is no oracle.swd.jre 1.1.8.10
    The workaround here is to use the Oracle Universal Installer installed onto
    your hard disk with the Oracle9i install, to install the Oracle 8.1.7
    components.
    Hope this helps

  • Can I use Oracle SQL Developer to "Move" data?

    Hello,
    I'm new to Oracle and I'm trying to use Oracle SQL Developer to export data from one table (on server A) to another table (on sever B). I'm able to create a .ldr file but I don't know how to use the .ldr file in Oracle SQL Developer? I would appreciate any help you can provide.
    Thanks!

    Hi,
    The name of tables are different ?
    If I understood then try this below:
    e.g:
    C:\> exp user/password@connectionA file=maytable.dmp tables=SAFETYADMIN_TBL_0022_43
    C:\> imp user/password@connectionB file=mytable.dmp full=y
    After this import, then you can:
    [pre]
    C:\>sqlplus user/password@connectionB
    SQL> insert into SAFETYUSER_TBL_0022_44
         select * from SAFETYADMIN_TBL_0022_43;
    SQL> drop table SAFETYADMIN_TBL_0022_43;Feedback if this is not that you want.
    Cheers

  • Oracle Designer User Manual

    Hi Friends,
    I plan to learn Oracle Designer, Please help me to get Documentation(Pdf,.doc).
    I searched lot in Google, but no use.
    Regards,
    Kishore

    I'm not surprised that Google didn't tell you much - Oracle Designer was never a really popular product, and now is slowly dying. Which makes me wonder why you want to learn Designer? Don't get me wrong, it's a great product, and I'm REALLY sorry that Oracle isn't developing it further. Still, I would suggest that SQL Developer Data Modeling, or the UML-based design tools built into JDeveloper are probably better long term choices for the newbie, even though they don't have much in the way of application generation capabilities.
    As for documentation - when you install Designer you will get a good amount of documentation installed with it. Pay special attention to the Help files - these are really quite good IMHO. Beyond this, check out the Designer pages on OTN at http://www.oracle.com/technology/products/designer/index.html where you will find links to the Oracle documentation, and a few white papers and tutorials.
    For third party sources, look at the book, Oracle Designer Handbook by Paul Dorsey and Peter Koletzke. This was written for Designer 2.1, but a lot of it is still valid for the current version. And EVERY Designer user should be a member of the Oracle Development Tools Users Group (ODTUG) - the Designer white papers on the ODTUG website, http://www.odtug.com/ will give you information that isn't in the official documentation. That is especially true if you'll be using the versioning capabilities of Designer. It's worth the price of membership, but if you can't afford that, you can become an associate member for free and get access to most of the papers.

Maybe you are looking for