Blocking locks encountered while splitting partitions in 11g

Background: I've taken over administration of a database that has several date-range partitioned tables that, suffering from a lack of proper administration, have not had their MAXVALUE partition split into the requisite monthly partitions, in almost a year. As a result, in some cases the MAXVALUE partition has 10 million rows (the monthly partitions should average 750K rows).
My understanding is that the syntax I am using to perform the split, should allow for on-line access to the tables while the split is being performed. Here is my syntax without the actual table names:
ALTER TABLE owner.table_name
SPLIT PARTITION MAXVALUE AT
(TO_DATE(' 2012-02-01 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
INTO (PARTITION PART201201
TABLESPACE tablespace
PCTFREE 10
INITRANS 1
MAXTRANS 255,
PARTITION MAXVALUE) update indexes;
Problem: In attempting to split the MAXVALUE partition into monthly partitions while the database is on-line and accessible, I see application sessions being blocked by my split session.
So, is my understanding above incorrect? Is there some additional syntax that I am missing? Or, are the blocking locks I'm seeing merely transient in nature, and can be ignored? The server I'm running on is not very "beefy", and the split is taking quite a while to run.
Any assistance would be appreciated.

>
Background: I've taken over administration of a database that has several date-range partitioned tables that, suffering from a lack of proper administration, have not had their MAXVALUE partition split into the requisite monthly partitions, in almost a year. As a result, in some cases the MAXVALUE partition has 10 million rows (the monthly partitions should average 750K rows).
My understanding is that the syntax I am using to perform the split, should allow for on-line access to the tables while the split is being performed.
Problem: In attempting to split the MAXVALUE partition into monthly partitions while the database is on-line and accessible, I see application sessions being blocked by my split session.
So, is my understanding above incorrect? Is there some additional syntax that I am missing? Or, are the blocking locks I'm seeing merely transient in nature, and can be ignored? The server I'm running on is not very "beefy", and the split is taking quite a while to run.
>
DML that modifies the table cannot be performed on the table while the split is ongoing.
Your bigger problem is that you are using the WRONG method for your use case. If you repeatedly split the MAXVALUE partition you will be repeatedly copying and moving the same ultimate MAXVALUE data over and over again.
DBMS_REDEFINITION is one of your options. But since I just answered this same question 3 days ago see my reply in this thread for a more thorough discussion of your options.
Re: Which is the Best method to Split Partition

Similar Messages

  • Segment space while splitting partition

    Hello,
    I am using Oracle Database version, 11.2.0.2
    I am facing issue while splitting non-empty partitions.
    Issue:
    While splitting the non-empty partitions, oracle by default assigning segment space of 8MB. On the other hand, while I split empty partition or create the new partition, it does not get the segment space.
    I am using range partitions, and requirement is such we need to create daily partitions. So, this eats up a lot of space of database and I want to avoid this.
    I checked on internet, its been written that one parameter is causing this change. i.e. "_partition_large_extents"
    I alter the session and put the above parameter as 'false', but still it doesn't help.
    Let me know, what I can do, while splitting partition and deferring the segment space.
    Thanks in advance

    Hi,
    It is discussed in bug
    Bug 12415287 - DEFERRED SEGMENT CREATION DOES NOT WORK ON SPLIT PARTITION
    As per the bug, this issue will be fixed in 11.2.0.4 version.
    Thanks,
    Krishna

  • Using OleDbDataAdapter Update with InsertCommands and getting blocking locks on Oracle table

    The following code snippet shows the use of OleDbDataAdapter with InsertCommands.  This code is producing many inserts on the Oracle table and is now suffering from contention... all on the same table.  How does the OleDbDataAdapter produce
    inserts from a dataset... what characteristics do these inserts inherent in terms of batch behavior... or do they naturally contend for the same resource. 
    oc.Open();
    for (int i = 0; i < xImageId.Count; i++)
    // Create the oracle adapter using a SQL which will not return any actual rows just the structure
    OleDbDataAdapter da =
       new OleDbDataAdapter("SELECT BUSINESS_UNIT, INVOICE, ASSIGNMENT_ID, END_DT, RI_TIMECARD_ID, IMAGE_ID, FILENAME, BARCODE_LABEL_ID, " +
       "DIRECT_INVOICING, EXCLUDE_FLG, DTTM_CREATED, DTTM_MODIFIED, IMAGE_DATA, PROCESS_INSTANCE FROM sysadm.PS_RI_INV_PDF_MERG WHERE 1 = 2", oc);
    // Create a data set
    DataSet ds = new DataSet("documents");
    da.Fill(ds, "documents");
    // Loop through invoices and write to oracle
    string[] sInvoices = invoiceNumber.Split(',');
    foreach (string sInvoice in sInvoices)
        // Create a data set row
        DataRow dr = ds.Tables["documents"].NewRow();
        ... map the data
        // Populate the dataset
        ds.Tables["documents"].Rows.Add(dr);
    // Create the insert command
    string insertCommandText =
        "INSERT /*+ append */ INTO PS_table " +
        "(SEQ_NBR, BUSINESS_UNIT, INVOICE, ASSIGNMENT_ID, END_DT, RI_TIMECARD_ID, IMAGE_ID, FILENAME, BARCODE_LABEL_ID, DIRECT_INVOICING, " +
        "EXCLUDE_FLG, DTTM_CREATED, DTTM_MODIFIED, IMAGE_DATA, PROCESS_INSTANCE) " +
        "VALUES (INV.nextval, :BUSINESS_UNIT, :INVOICE, :ASSIGNMENT_ID, :END_DT, :RI_TIMECARD_ID, :IMAGE_ID, :FILENAME,  " +
        ":BARCODE_LABEL_ID, :DIRECT_INVOICING, :EXCLUDE_FLG, :DTTM_CREATED, :DTTM_MODIFIED, :IMAGE_DATA, :PROCESS_INSTANCE)";
    // Add the insert command to the data adapter
    da.InsertCommand = new OleDbCommand(insertCommandText);
    da.InsertCommand.Connection = oc;
    // Add the params to the insert
    da.InsertCommand.Parameters.Add(":BUSINESS_UNIT", OleDbType.VarChar, 5, "BUSINESS_UNIT");
    da.InsertCommand.Parameters.Add(":INVOICE", OleDbType.VarChar, 22, "INVOICE");
    da.InsertCommand.Parameters.Add(":ASSIGNMENT_ID", OleDbType.VarChar, 15, "ASSIGNMENT_ID");
    da.InsertCommand.Parameters.Add(":END_DT", OleDbType.Date, 0, "END_DT");
    da.InsertCommand.Parameters.Add(":RI_TIMECARD_ID", OleDbType.VarChar, 10, "RI_TIMECARD_ID");
    da.InsertCommand.Parameters.Add(":IMAGE_ID", OleDbType.VarChar, 8, "IMAGE_ID");
    da.InsertCommand.Parameters.Add(":FILENAME", OleDbType.VarChar, 80, "FILENAME");
    da.InsertCommand.Parameters.Add(":BARCODE_LABEL_ID", OleDbType.VarChar, 18, "BARCODE_LABEL_ID");
    da.InsertCommand.Parameters.Add(":DIRECT_INVOICING", OleDbType.VarChar, 1, "DIRECT_INVOICING");
    da.InsertCommand.Parameters.Add(":EXCLUDE_FLG", OleDbType.VarChar, 1, "EXCLUDE_FLG");
    da.InsertCommand.Parameters.Add(":DTTM_CREATED", OleDbType.Date, 0, "DTTM_CREATED");
    da.InsertCommand.Parameters.Add(":DTTM_MODIFIED", OleDbType.Date, 0, "DTTM_MODIFIED");
    da.InsertCommand.Parameters.Add(":IMAGE_DATA", OleDbType.Binary, System.Convert.ToInt32(filedata.Length), "IMAGE_DATA");
    da.InsertCommand.Parameters.Add(":PROCESS_INSTANCE", OleDbType.VarChar, 10, "PROCESS_INSTANCE");
    // Update the table
    da.Update(ds, "documents");

    Here is what Oracle is showing as blocking locks and the SQL that has been identified with each of the SIDS.  Not sure why there is contention.  There are no triggers or joined tables in this piece of code.
    Here is the SQL all of the SIDs below are running:
    INSERT INTO sysadm.PS_RI_INV_PDF_MERG (SEQ_NBR, BUSINESS_UNIT, INVOICE, ASSIGNMENT_ID, END_DT, RI_TIMECARD_ID, IMAGE_ID, FILENAME, BARCODE_LABEL_ID, DIRECT_INVOICING, EXCLUDE_FLG, DTTM_CREATED, DTTM_MODIFIED, IMAGE_DATA, PROCESS_INSTANCE) VALUES (SYSADM.INV_PDF_MERG.nextval,
    :BUSINESS_UNIT, :INVOICE, :ASSIGNMENT_ID, :END_DT, :RI_TIMECARD_ID, :IMAGE_ID, :FILENAME, :BARCODE_LABEL_ID, :DIRECT_INVOICING, :EXCLUDE_FLG, :DTTM_CREATED, :DTTM_MODIFIED, :IMAGE_DATA, :PROCESS_INSTANCE)
    SID 1452 (BTSUSER,BIZTPRDI,BTSNTSvc64.exe) in instance FSLX1 is blocking SID 1150 (BTSUSER,BIZTPRDI,BTSNTSvc64.exe) in instance FSLX1
    SID 1452 (BTSUSER,BIZTPRDI,BTSNTSvc64.exe) in instance FSLX1 is blocking SID 1452 (BTSUSER,BIZTPRDI,BTSNTSvc64.exe) in instance FSLX1
    SID 1452 (BTSUSER,BIZTPRDI,BTSNTSvc64.exe) in instance FSLX1 is blocking SID 1156 (BTSUSER,biztprdi,BTSNTSvc64.exe) in instance FSLX3
    SID 1452 (BTSUSER,BIZTPRDI,BTSNTSvc64.exe) in instance FSLX1 is blocking SID 6 (BTSUSER,BIZTPRDI,BTSNTSvc64.exe) in instance FSLX2
    SID 1452 (BTSUSER,BIZTPRDI,BTSNTSvc64.exe) in instance FSLX1 is blocking SID 1726 (BTSUSER,BIZTPRDI,BTSNTSvc64.exe) in instance FSLX2
    SID 1452 (BTSUSER,BIZTPRDI,BTSNTSvc64.exe) in instance FSLX1 is blocking SID 2016 (BTSUSER,biztprdi,BTSNTSvc64.exe) in instance FSLX2

  • Blocking Locks - What Was Likely Going On?

    I had a blocking lock yesterday that showed up in OEM under Cluster Database --> Cluster Database Locks. The blocking lock was a row exclusive (RX) table lock that was blocking 175 other sessions that were listed under the blocking lock as having requested row share (RS) locks. It was an hour before I found out about this problem.
    Two questions:
    1.] The "Oracle Database Concepts 10gR2" book, Table 13-13, states that a row exclusive (RX) table lock can be obtained as a result of INSERT, UPDATE or DELETE DML and that in RX mode share lock modes are not permitted (which is why I had 175 blocked sessions). Does this mean that a user must have been doing a long running (1 hour plus) INSERT, UPDATE or DELETE or is there another more likely cause that I'm not aware of?
    2.] The only ways I know of to request a row share lock (of which 175 were blocked due to the RX lock) is by using:
    LOCK_TABLE <table name> IN SHARE MODE;
    LOCK_TABLE <table name> IN SHARE EXCLUSIVE MODE;
    LOCK_TABLE <table name> IN EXCLUSIVE MODE;
    I can't imagine a user doing any of these commands so is there another more likely reason that 175 row share (RX) locks were being requested (and blocked)?
    Thanks for any insight you can offer. I ended up killing the session that held the RX lock and that resolved the problem but I'd like to better understand what was happening.

    1.] The "Oracle Database Concepts 10gR2" book, Table
    13-13, states that a row exclusive (RX) table lock
    can be obtained as a result of INSERT, UPDATE or
    DELETE DML and that in RX mode share lock modes are
    not permittedThat table shows that RS (mode 2) is permitted while RX lock is held.
    Did you mean to say that sessions were waiting on a S mode (4) lock?
    This could indicate that update/delete was attempted on a parent table and that dependend table was lacking an index on fk column. (may answer your q.2)

  • Dead lock and Blocking Lock

    I would like to understand what is major difference between Dead Locks and Blocking Locks in Oracle. If someone could explain or point me to good web Link I would really appreciate
    Thanks.

    Tony's advise is very good.
    In simple terms a blocking lock is a lock being held by one session that is preventing another session from performing an DML operation on the same data until the holding session commits or rollbacks.
    A deadlock is a situation where two or more sessions lock data in such a manner as each session is waiting on a resource held by another session so that none of the session can complete their unit of work. That is session A locks row 1 then session B locks row 2 followed by session A attempts to lock row 2 while session B now attemps to lock row 1. Neither session A or B will ever be able to complete thier transaction releasing the locks and allowing waiting sessions to process since each session is waiting on a resource that the other session has while holding a resource the other session needs. In other words a deadlock. Oracle detects deadlocks and kills one of the sessions freeing resources.
    HTH -- Mark D Powell --

  • A Critical error encountered while loading webpage.

    Was running 2.1.51  and when browsing to the status link while logged in to the web gui I got a blank web page with the following text:
    A Critical error encountered while loading webpage.
    Reboot router - log back in - can go anywhere except the status page -- get same error page
    made the mistake of downloading and upgrading firmware to 2.1.71   = upgrade completed successfully = presented with the new login screen confirming that the box is running the new code -- now when I log in - I don't get in rather the previous error page - and cant get anywhere.
    A Critical error encountered while loading webpage.
    the url is https://192.168.75.1/scgi-bin/platform.cgi   but it doesn't load only displays the error.
    could someone share another valid management url for the box so I can at least try to get in somewhere before attempting to factory reset this POS ;-(
    thanks.

    Thanks for the response.   Based on the number of crickets that I heard after asking the question, I did indeed factory reset the box.  Luckily I had a backup of the config so it wasn't too painful to restore.
    I beleive the root cause co-incided with the expiration of the trend micro web protection gateway service.
    For whatever reason, I did not receive any notification that the service was to expire but the error experienced was noticed just two days after the subscription expired...  I had successfully logged in without issue and was able to view the status tab only a week earlier.
    be sure to pay the cisco tax on time or they'll lock you out of your box was the lesson learned...

  • Adapter error encountered while updating UD_ADUSER_LNAME

    Hi,
    As a field upadted on OIM user form, While updating the same on target AD, we encounter the following error randomly in OIM 11g
    Adapter error encountered while updating UD_ADUSER_LNAME.Setting task status...
    *"DATABASE_ERROR" does not correspond to a known Response Code. Using "UNKNOWN*".
    Earlier if any one had faced the same issue. Please help.
    Regads,
    Anil Bansal

    Check the field size. Make sure it doesn't exceed to the entered value.
    -Prakash

  • Errors encountered while doing BCC Full deployment in the Applying phase

    Errors encountered while doing BCC Full deployment in the Applying phase. The stack trace is as below:-
    **** Warning    Fri Aug 02 09:43:24 BST 2013    1375433004207   /atg/epub/PublishingRepository  Using default JDBC type for: project:tar814 could not find this column in the table's meta data
    **** debug      Fri Aug 02 09:52:54 BST 2013    1375433574278   /atg/epub/DeploymentServer      Run first apply phase: true
    **** debug      Fri Aug 02 09:52:54 BST 2013    1375433574279   /atg/epub/DeploymentServer      Switch switchable CA datasources:
    **** debug      Fri Aug 02 09:52:54 BST 2013    1375433574279   /atg/epub/DeploymentServer        isDeploymentRollback(): false
    **** debug      Fri Aug 02 09:52:54 BST 2013    1375433574284   /atg/epub/DeploymentServer        Current Target live datasource name: DataSourceA
    **** debug      Fri Aug 02 09:52:54 BST 2013    1375433574285   /atg/epub/DeploymentServer        CA switching datasource: /atg/commerce/jdbc/ProductCatalogSwitchingDataSource_production
    **** debug      Fri Aug 02 09:52:54 BST 2013    1375433574285   /atg/epub/DeploymentServer          Current live datasource name: DataSourceB
    **** debug      Fri Aug 02 09:52:54 BST 2013    1375433574285   /atg/epub/DeploymentServer          Current offline datasource name: DataSourceA
    **** debug      Fri Aug 02 09:52:54 BST 2013    1375433574286   /atg/epub/DeploymentServer          The current CA live datasource is pointing at the Target offline datasource. No CA switch necessary.
    **** debug      Fri Aug 02 09:52:54 BST 2013    1375433574287   /atg/epub/DeploymentServer      Switchable CA datasources switched.
    **** info       Fri Aug 02 09:52:54 BST 2013    1375433574307   /atg/epub/DeploymentServer      DirectSQLReplicationAdapter: Starting FIRST phase data transfer.
    **** Error      Fri Aug 02 09:53:12 BST 2013    1375433592737   /com/screwfix/content/block/BlockRepository-ver SQL Statement Failed: [++ReplicationSQL++]
    **** Error      Fri Aug 02 09:53:12 BST 2013    1375433592737   /com/screwfix/content/block/BlockRepository-ver INSERT
    **** Error      Fri Aug 02 09:53:12 BST 2013    1375433592737   /com/screwfix/content/block/BlockRepository-ver INTO ndcatalog2.extn_block_link
    **** Error      Fri Aug 02 09:53:12 BST 2013    1375433592737   /com/screwfix/content/block/BlockRepository-ver      (
    **** Error      Fri Aug 02 09:53:12 BST 2013    1375433592737   /com/screwfix/content/block/BlockRepository-ver        renderer_id,
    **** Error      Fri Aug 02 09:53:12 BST 2013    1375433592737   /com/screwfix/content/block/BlockRepository-ver        link,
    **** Error      Fri Aug 02 09:53:12 BST 2013    1375433592737   /com/screwfix/content/block/BlockRepository-ver        block_id
    **** Error      Fri Aug 02 09:53:12 BST 2013    1375433592737   /com/screwfix/content/block/BlockRepository-ver      )
    **** Error      Fri Aug 02 09:53:12 BST 2013    1375433592737   /com/screwfix/content/block/BlockRepository-ver SELECT
    **** Error      Fri Aug 02 09:53:12 BST 2013    1375433592737   /com/screwfix/content/block/BlockRepository-ver        t1.renderer_id,
    **** Error      Fri Aug 02 09:53:12 BST 2013    1375433592737   /com/screwfix/content/block/BlockRepository-ver        t1.link,
    **** Error      Fri Aug 02 09:53:12 BST 2013    1375433592737   /com/screwfix/content/block/BlockRepository-ver        t1.block_id
    **** Error      Fri Aug 02 09:53:12 BST 2013    1375433592737   /com/screwfix/content/block/BlockRepository-ver FROM
    **** Error      Fri Aug 02 09:53:12 BST 2013    1375433592737   /com/screwfix/content/block/BlockRepository-ver        extn_block_link t1,
    **** Error      Fri Aug 02 09:53:12 BST 2013    1375433592737   /com/screwfix/content/block/BlockRepository-ver        extn_block t2
    **** Error      Fri Aug 02 09:53:12 BST 2013    1375433592737   /com/screwfix/content/block/BlockRepository-ver WHERE t2.asset_version =
    **** Error      Fri Aug 02 09:53:12 BST 2013    1375433592737   /com/screwfix/content/block/BlockRepository-ver        ( SELECT MAX ( asset_version )
    **** Error      Fri Aug 02 09:53:12 BST 2013    1375433592737   /com/screwfix/content/block/BlockRepository-ver          FROM extn_block
    **** Error      Fri Aug 02 09:53:12 BST 2013    1375433592737   /com/screwfix/content/block/BlockRepository-ver          WHERE
    **** Error      Fri Aug 02 09:53:12 BST 2013    1375433592737   /com/screwfix/content/block/BlockRepository-ver            (
    **** Error      Fri Aug 02 09:53:12 BST 2013    1375433592737   /com/screwfix/content/block/BlockRepository-ver              (
    **** Error      Fri Aug 02 09:53:12 BST 2013    1375433592737   /com/screwfix/content/block/BlockRepository-ver                checkin_date <= ?
    **** Error      Fri Aug 02 09:53:12 BST 2013    1375433592737   /com/screwfix/content/block/BlockRepository-ver              )
    **** Error      Fri Aug 02 09:53:12 BST 2013    1375433592737   /com/screwfix/content/block/BlockRepository-ver            )
    **** Error      Fri Aug 02 09:53:12 BST 2013    1375433592737   /com/screwfix/content/block/BlockRepository-ver            AND branch_id = ?
    **** Error      Fri Aug 02 09:53:12 BST 2013    1375433592737   /com/screwfix/content/block/BlockRepository-ver            AND block_id = t2.block_id
    **** Error      Fri Aug 02 09:53:12 BST 2013    1375433592737   /com/screwfix/content/block/BlockRepository-ver        )
    **** Error      Fri Aug 02 09:53:12 BST 2013    1375433592737   /com/screwfix/content/block/BlockRepository-ver AND t2.version_deleted = ?
    **** Error      Fri Aug 02 09:53:12 BST 2013    1375433592737   /com/screwfix/content/block/BlockRepository-ver AND t2.branch_id = ?
    **** Error      Fri Aug 02 09:53:12 BST 2013    1375433592737   /com/screwfix/content/block/BlockRepository-ver AND t1.asset_version =  t2.asset_version
    **** Error      Fri Aug 02 09:53:12 BST 2013    1375433592737   /com/screwfix/content/block/BlockRepository-ver AND t1.block_id = t2.block_id
    **** Error      Fri Aug 02 09:53:12 BST 2013    1375433592737   /com/screwfix/content/block/BlockRepository-ver
    **** Error      Fri Aug 02 09:53:12 BST 2013    1375433592737   /com/screwfix/content/block/BlockRepository-ver -- Parameters --
    **** Error      Fri Aug 02 09:53:12 BST 2013    1375433592737   /com/screwfix/content/block/BlockRepository-ver p[1] = {pd: checkin_date} 2013-07-30 10:23:57.867 (java.sql.Timestamp)
    **** Error      Fri Aug 02 09:53:12 BST 2013    1375433592737   /com/screwfix/content/block/BlockRepository-ver p[2] = {pd: branch_id} 10500 (java.lang.String)
    **** Error      Fri Aug 02 09:53:12 BST 2013    1375433592737   /com/screwfix/content/block/BlockRepository-ver p[3] = {pd: version_deleted} false (java.lang.Boolean)
    **** Error      Fri Aug 02 09:53:12 BST 2013    1375433592737   /com/screwfix/content/block/BlockRepository-ver p[4] = {pd: branch_id} 10500 (java.lang.String)
    **** Error      Fri Aug 02 09:53:12 BST 2013    1375433592737   /com/screwfix/content/block/BlockRepository-ver [--ReplicationSQL--]
    **** Error      Fri Aug 02 09:53:12 BST 2013    1375433592737   /com/screwfix/content/block/BlockRepository-ver         java.sql.SQLSyntaxErrorException: ORA-00904: "RENDERER_ID": invalid identifier
    Please note that we are migrating from ATG 2007 to ATG 10.0.1...Also we are doing deployment in this new environment for the first time only.
    Thanks a lot
    Pijush

    Hi Pijush,
    The exception towards the end of the stack trace says the RENDERER_ID is an invalid identifier. the Oracle error 00904 indicates the column name must be wrong. Can you verify the repostiory xml on the BlockRepository and check the column name.
    Regards,
    Srikanth

  • Question for Ali Brown about split partition

    Ali:
    I thought that I was posting a new topic by changing the subject line but I saw that it didn't work--but it was already up in lights . . . . It's an amazing race, eh? Thanks for your previous reply, glad it's easy to do--please, informa me . . . . While replying to Warren P about his printer issues I saw that you are running a split partition in one of your computers. I have an Imac G4 with 10.1.5/9.22 that perhaps one day I'd like to bring up to 10.3.9, but keeping the OS 9 side intact. Is that a GUI type exercise or did it take a special program? I haven't look at Disc Util in my iMac to see how that might be done, nor have I searched Apple Database . . .. Seeing your hardware info just piqued my curiosity. Any links to info about how to do what you did?? Thanks.
    eep

    Hi Again eep!
    As I posted in the previous topic, my HD is not partitioned.
    OS 9 & OS X exist together, and my iMac is Dual-Boot.
    When I upgraded from 10.1.5, I did a Simple Update to Panther 10.3.x, and eventually updated to 10.3.9.
    Some info in these links:
    Mac OS X 10.3 installation (FAQ).
    About installation options. Basically the same for Panther 10.3.x.
    Tiger is available for purchase at The Apple Store (U.S.).
    Panther, is no longer available directly from the Apple Online Store, as Tiger 10.4.x is the most up to date OS.
    If you know what to look for, a Full Retail Version, of the Panther Install CDs, or a Full Retail Version, of the Tiger Install DVD, can also be purchased rather inexpensively, at some online Apple retailers, Amazon, eBay, AppleRescue, FastMac, etc.
    Be sure not to purchase grey, upgrade or machine specific CDs or DVDs.
    Panther is only on CDs, not DVDs.
    Unless purchased from AppleRescue, the discs should look exactly like the images in the above links, and not say Upgrade on them.
    Additional info in these links.
    Using OS X Install CDs/DVDs On Multiple Macs
    What's A Computer Specific Mac OS X Release
    Software Update, Upgrade: What's The Difference?
    Before upgrading to any OS X version, check to see if your Mac needs a Firmware Update.
    If one is required, you must start the computer from a Mac OS 8 or Mac OS 9 System Folder on the computer's hard disk, not from a CD, in order to install it.
    Once Panther 10.3.x is installed, you can use the 10.3.9 Combo Update, to upgrade to the final version.
    If your Mac meets the System Requirements for Tiger, you could also consider installing that.
    And then use the PPC 10.4.8 Combo Update, to upgrade to the current version.
    Panther System Requirements
    Additional Panther System Requirements
    Tiger System Requirements
    Additionally, "Tiger ships on a DVD, but if your Mac doesn’t have a built-in DVD-ROM player, you’ll need CD media. When you buy Mac OS X Tiger, you qualify to purchase Tiger CDs for only $9.95."
    Download the Media Exchange Program Order From Here.
    Orders must be mailed by March 19, 2007.
    AppleRescue, also sells a Tiger installation set on CD
    Shop Carefully, Examine All Documentation, And Good Luck!
    ali b

  • SQL Timeouts and Blocking Locks

    SQL Timeouts and Blocking Locks
    Just wanted to check in and see if anyone here has feedback on application settings, ColdFusion settings, JBOSS settings or other settings that could help to limit or remove SQL Timeouts and blocking locks on SID's.
    We're using MS SQL 2000 with JBOSS and IIS5.
    We've been seeing the following error in our logs that starts blocking locks in SQL:
    java.sql.SQLException: [newScale] [SQLServer JDBC Drive] [SQLServer] Lock request time out period exceeded.
    Once this happens, we're hosed until we remove the blocking SID in SQL.  These are the connections to the application.
    Any feedback would be great.  Thanks!

    Hi
    This is your exact solution:
    Select a.username, a.sid, a.serial#, b.id1, c.sql_text
    From v$session a, v$lock b, v$sqltext c
    Where b.id1 in( Select distinct e.id1
    from v$session d , v$lock e
    where d.lockwait = e.kaddr ) and
    a.sid = b.sid and
    c.hash_value = a.sql_hash_value and
    b.request =0;
    Thanks
    Sarju
    Oracle DBA
    <BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>Originally posted by I'm clueless:
    Can someone give me the SQL statement to
    show if there are any blocking database locks and if so - which user is locking the Database?
    Thanks in Advance<HR></BLOCKQUOTE>
    null

  • Signal 4 error encountered while running a customized report

    Signal 4 error encountered while running a customized report
    We are running Oracle Applications version 11.5.10 on Oracle RDBMS 9.2.0. and IBM AIX 5.3 o production system and AIX 5.2 on test machines. We have made a new clone of production database on test machine and after installation of a clone on test-machine all customized reports terminated with signal 4 error.
    Can anybody tell the possible causes of signal 4 errors and their remidies ?

    Thank you for the link, i will read it...
    I have problemss with PDF output...
    When trying to run any concurrent request with PDF output, it completed with error and show the following message in the request log file:
    Current NLS_LANG and NLS_NUMERIC_CHARACTERS Environment Variables are :
    American_America.AR8MSWIN1256
    Spawned Process 499776
    stat_low =84
    stat_high = 0
    emsg:was terminated by signal 4
    Program was terminated by signal 4
    Concurrent Manager encountered an error while running Oracle*Report for your concurrent request 20824997

  • Exception Encountered while attempting to send message[JMSExceptions:045103

    Hi - I need help on one the issue I am facing. It seems some minor mistake but unable to find that.
    I have a EJB code deployed on weblogic. I am using OSB business service to invoke EJB and publish data to JMS. I have setup all queue and JNDI properly but for some reason, I am keep on getting below error. I have google and fond couple of doc but all point to JMS server down .. I am able to access that queue through normal OSB project and able to publish data in it..
    Could someone pls what could be wrong I am doing.
    Error:-
    Exception Encountered while attempting to send message[JMSExceptions:045103]While trying to find a topic or a queue we could not find the specific JMSServer requested. The linked exception may contain more information about the reason for failure.

    Restart the server and the SQL Services and Hosts associated. Remove the Dll's from the GAC and re-build and Deploy. This sort of issue might occur due to some cache, Permission or some errors in the odx at run time.
    Also, refer the blog http://atinag.wordpress.com/category/biztalk-server/,  which explains about the similar sort of issue.
    Regards - Rajasekhar.R
    Don't forget to mark the post as answer or vote as helpful if it does,

  • Monitoring blocking Locks

    Hi
    This question relates to monitoring blocking locks on a 9.2.0.5 2 node RAC
    Origionally I have been monitoring bocking locks with every 5 mins using the following query:
    "select * from dba_blockers"
    I have recently implemented monitoring via grid control this is running an out of the box metric every 5 mins, the sql behind it is as follows:
    "SELECT blocking_sid, num_blocked
    FROM ( SELECT blocking_sid, SUM(num_blocked) num_blocked
    FROM ( SELECT l.id1, l.id2,
    MAX(DECODE(l.block, 1, i.instance_name||'-'||l.sid,
    2, i.instance_name||'-'||l.sid, 0 )) blocking_sid,
    SUM(DECODE(l.request, 0, 0, 1 )) num_blocked
    FROM gv$lock l, gv$instance i
    WHERE ( l.block!= 0 OR l.request > 0 ) AND
    l.inst_id = i.inst_id
    GROUP BY l.id1, l.id2)
    GROUP BY blocking_sid
    ORDER BY num_blocked DESC)
    WHERE num_blocked != 0 "
    Now.. At one point today the alert using "select * from dba_blockers" fired where as the out of the box metric from gird control did not fire.... alert duration was around 5 - 10 mins
    At first i simply assumed that this could have been a brief lock and due to both 5 min intervals being out of sync, the lock had shown and cleared before the grid control interval run.
    now im a little more curious.
    Is there any significan difference in what these 2 different SQL's will alert on, I was under the impression that DBA_BLOCKERS was simply querying a number of joined views, and Oracle had decided to use V$lock for their out of the box metric as it was more efficient.
    Any comments welcome
    Thanks

    Just to prove that the SQL is correct I have constrcuted a demo for you...
    SQL> create table t (a char(1));
    Table created.
    SQL> insert into t values ('z');
    1 row created.
    SQL> commit;
    in session 1 ---->
    select * from t where a='z' for update;
    ==================================================================
    in session 2 ---->
    update t set a='x' where a='z';
    (session simply hangs)
    ==================================================================
    in session 3 ------>
    SQL> select * from dba_blockers;
    HOLDING_SESSION
    48
    SQL>
    SQL> SELECT blocking_sid, num_blocked
    FROM ( SELECT blocking_sid, SUM(num_blocked) num_blocked
    FROM ( SELECT l.id1, l.id2, MAX(DECODE(l.block, 1, i.instance_name||'-'||l.sid,
    2, i.instance_name||'-'||l.sid, 0 )) blocking_sid,
    SUM(DECODE(l.request, 0, 0, 1 )) num_blocked
    FROM gv$lock l, gv$instance i
    WHERE ( l.block!= 0 OR l.request > 0 ) AND
    l.inst_id = i.inst_id
    GROUP BY l.id1, l.id2)
    GROUP BY blocking_sid
    ORDER BY num_blocked DESC)
    WHERE num_blocked != 0;
    2 3 4 5 6 7 8 9 10 11 12
    BLOCKING_SID NUM_BLOCKED
    RAC1-48 1
    So back to the origional question,
    I am using both these queries from different monitors on my prod syystem, both running on 5 minute intervals, " select * from dba_blockers" fired where as the above query - querying gv$lock did not fire.
    Origionaly i assumed that the blocking lock may have simply lasted 3t0 seconds, and due the 5 minute monitor intervals of each metric not being in sync, ... "select * from dba_blockers" may have picked up the lock, then the query selecting from gv$lock ran 2 mins later by which time the lock had disapeared.
    -Can anyone suggest any other reasons other than this why one monitor (select * from dba_blockers) picked up the lock and the other (gv$lock) didnt?
    Thanks

  • Monitoring Blocking locks (dba_blockers vs v$lock)

    Hi
    This question relates to monitoring blocking locks on a 9.2.0.5 database
    Origionally I have been monitoring bocking locks with every 5 mins using the following query:
    "select * from dba_blockers"
    I have recently implemented monitoring via grid control this is running an out of the box metric every 5 mins, the sql behind it is as follows:
    "SELECT blocking_sid, num_blocked
    FROM ( SELECT blocking_sid, SUM(num_blocked) num_blocked
    FROM ( SELECT l.id1, l.id2,
    MAX(DECODE(l.block, 1,l.sid,
    2,l.sid, 0 )) blocking_sid,
    SUM(DECODE(l.request, 0, 0, 1 )) num_blocked
    FROM v$lock l
    WHERE ( l.block!= 0 OR l.request > 0 ) AND
    GROUP BY l.id1, l.id2)
    GROUP BY blocking_sid
    ORDER BY num_blocked DESC)
    WHERE num_blocked != 0 "
    Now.. At one point today the alert using "select * from dba_blockers" fired where as the out of the box metric from gird control did not fire.... alert duration was around 5 - 10 mins
    At first i simply assumed that this could have been a brief lock and due to both 5 min intervals being out of sync, the lock had shown and cleared before the grid control interval run.
    now im a little more curious.
    Is there any significan difference in what these 2 different SQL's will alert on (different types of blocking locks / sessions?) , I was under the impression that DBA_BLOCKERS was simply querying a number of joined views, and Oracle had decided to use V$lock for their out of the box metric as it was more efficient.
    Any comments welcome
    Thanks

    Re: Monitoring blocking Locks

  • Blocking locks by user report hangs

    Please,
    "Blocking locks by user" report under "Database Administration Section" of "Data Dictionary Reports" is hanging
    every time we try to run it against any database.
    Please, confirm this issue in Oracle Sql Developer 4.0 EA since it was working perfectly in
    Oracle SQL Developer 3.2.2 (3.2.20.09.87).
    Also, allow us an estimate deadline for correction.
    Thanks in advance,
    Andraly Ng

    please make a copy of the posting in the report-forum

Maybe you are looking for