SDO_PC blocks partition

Hi,
I am trying to create SDO_PC and I want to sort points in blocks via three dimensions. I was not succesfull and need advice ho to do it.
DECLARE
pc SDO_PC;
BEGIN
pc := SDO_PC_PKG.INIT(
'base',
'PC',
'PC_BLKTAB2',
'blk_capacity=50000',
SDO_GEOMETRY(3003, NULL, NULL,
SDO_ELEM_INFO_ARRAY(1,1003,3),
SDO_ORDINATE_ARRAY(-1800000, -1800000, -1800, 1800000, 1800000, 1800)
0.00005,
3,
NULL
INSERT INTO base (pc) VALUES (pc);
SDO_PC_PKG.CREATE_PC(
pc,
'entry'
END;
Error report:
ORA-13199: Invalid Parameters for Partition_Table
ORA-13199: Invalid Parameters for Partition_Table
ORA-13236: interní chyba při zpracovávání R-stromu: [failed to cluster in memory]
ORA-13249: Internal error in Spatial index: [mdrcrclmem]
ORA-13234: selhání přístupu do tabulky R-stromového indexu [error in lob insert]
ORA-29400: chyba zásobníku dat
ORA-29861: index domény je označen jako LOADING, FAILED nebo UNUSABLE
ORA-06512: na "MDSYS.PRVT_PC", line 3
ORA-06512: na "MDSYS.PRVT_PC", line 130
ORA-06512: na "MDSYS.SDO_PC_PKG", line 74
ORA-06512: na line 20
13199. 00000 - "%s"
*Cause: This is an internal error.
*Action: Contact Oracle Support Services.
Thanks
Kirin

I am able to create to block like this with no problems:
DECLARE
pc SDO_PC;
BEGIN
pc := SDO_PC_PKG.INIT(
'dotaz_kaple',
'PC',
'PC_BLKTAB3'
'blk_capacity=50',
SDO_GEOMETRY(2003, NULL, NULL,
SDO_ELEM_INFO_ARRAY(1,1003,3),
SDO_ORDINATE_ARRAY(-1800000, -1800000, 1800000, 1800000)
0.00005,
3,
NULL
INSERT INTO dotaz_kaple (pc) VALUES (pc);
SDO_PC_PKG.CREATE_PC(
pc,
'testovaci_blok'
END;
Data created this way have the attribute PT_SORT_DIM = 1. But I want to sort points in blocks via three dimensions.
I tried 1,1003,7 for elem info, but it is the same error. Blok size does not change anything.
Here are my data I am using
CREATE TABLE ENTRY (RID VARCHAR2(24),
     VAL_D1 NUMBER,
     VAL_D2 NUMBER,
     VAL_D3 NUMBER);
Insert into ENTRY (RID,VAL_D1,VAL_D2,VAL_D3) values (1,-812782.209,-1079712.135,395.232);
Insert into ENTRY (RID,VAL_D1,VAL_D2,VAL_D3) values (2,-812782.35,-1079712.102,395.38);
Insert into ENTRY (RID,VAL_D1,VAL_D2,VAL_D3) values (3,-812782.359,-1079712.224,395.309);
Insert into ENTRY (RID,VAL_D1,VAL_D2,VAL_D3) values (4,-812782.497,-1079712.178,395.233);
Insert into ENTRY (RID,VAL_D1,VAL_D2,VAL_D3) values (5,-812782.536,-1079712.239,395.381);
Insert into ENTRY (RID,VAL_D1,VAL_D2,VAL_D3) values (6,-812782.522,-1079712.376,395.312);
Insert into ENTRY (RID,VAL_D1,VAL_D2,VAL_D3) values (7,-812782.3,-1079712.121,388.091);
Insert into ENTRY (RID,VAL_D1,VAL_D2,VAL_D3) values (8,-812782.628,-1079712.196,395.507);
Insert into ENTRY (RID,VAL_D1,VAL_D2,VAL_D3) values (9,-812782.704,-1079712.145,395.635);
Insert into ENTRY (RID,VAL_D1,VAL_D2,VAL_D3) values (10,-812782.36,-1079712.25,388.088);
Insert into ENTRY (RID,VAL_D1,VAL_D2,VAL_D3) values (11,-812782.686,-1079712.367,395.376);
Insert into ENTRY (RID,VAL_D1,VAL_D2,VAL_D3) values (12,-812782.764,-1079712.15,395.423);
Insert into ENTRY (RID,VAL_D1,VAL_D2,VAL_D3) values (13,-812782.667,-1079712.45,395.22);
Insert into ENTRY (RID,VAL_D1,VAL_D2,VAL_D3) values (14,-812782.793,-1079712.287,395.562);
Insert into ENTRY (RID,VAL_D1,VAL_D2,VAL_D3) values (15,-812782.875,-1079712.183,395.766);
Insert into ENTRY (RID,VAL_D1,VAL_D2,VAL_D3) values (16,-812782.864,-1079712.155,395.301);
Insert into ENTRY (RID,VAL_D1,VAL_D2,VAL_D3) values (17,-812782.578,-1079712.183,388.833);
Insert into ENTRY (RID,VAL_D1,VAL_D2,VAL_D3) values (18,-812782.582,-1079712.145,388.633);
Insert into ENTRY (RID,VAL_D1,VAL_D2,VAL_D3) values (19,-812782.597,-1079712.117,388.331);
Insert into ENTRY (RID,VAL_D1,VAL_D2,VAL_D3) values (20,-812782.825,-1079712.474,395.384);
Insert into ENTRY (RID,VAL_D1,VAL_D2,VAL_D3) values (21,-812782.889,-1079712.299,395.419);
Insert into ENTRY (RID,VAL_D1,VAL_D2,VAL_D3) values (22,-812782.633,-1079712.137,388.094);
Insert into ENTRY (RID,VAL_D1,VAL_D2,VAL_D3) values (23,-812782.916,-1079712.35,395.593);
Insert into ENTRY (RID,VAL_D1,VAL_D2,VAL_D3) values (24,-812782.813,-1079712.592,395.23);
Insert into ENTRY (RID,VAL_D1,VAL_D2,VAL_D3) values (25,-812782.699,-1079712.103,388.494);
Insert into ENTRY (RID,VAL_D1,VAL_D2,VAL_D3) values (26,-812783.063,-1079712.129,395.849);
Insert into ENTRY (RID,VAL_D1,VAL_D2,VAL_D3) values (27,-812782.705,-1079712.242,388.866);
Insert into ENTRY (RID,VAL_D1,VAL_D2,VAL_D3) values (28,-812782.699,-1079712.232,388.665);
Insert into ENTRY (RID,VAL_D1,VAL_D2,VAL_D3) values (29,-812782.71,-1079712.145,388.23);
Insert into ENTRY (RID,VAL_D1,VAL_D2,VAL_D3) values (30,-812782.7,-1079712.235,388.358);
Insert into ENTRY (RID,VAL_D1,VAL_D2,VAL_D3) values (31,-812782.657,-1079712.319,388.092);
Insert into ENTRY (RID,VAL_D1,VAL_D2,VAL_D3) values (32,-812782.934,-1079712.51,395.238);
Insert into ENTRY (RID,VAL_D1,VAL_D2,VAL_D3) values (33,-812783.064,-1079712.26,395.738);
Insert into ENTRY (RID,VAL_D1,VAL_D2,VAL_D3) values (34,-812783.032,-1079712.292,395.289);
Insert into ENTRY (RID,VAL_D1,VAL_D2,VAL_D3) values (35,-812783.05,-1079712.201,394.953);
Insert into ENTRY (RID,VAL_D1,VAL_D2,VAL_D3) values (36,-812783.028,-1079712.22,394.607);
Insert into ENTRY (RID,VAL_D1,VAL_D2,VAL_D3) values (37,-812782.989,-1079712.536,395.485);
Insert into ENTRY (RID,VAL_D1,VAL_D2,VAL_D3) values (38,-812782.935,-1079712.637,395.113);
Insert into ENTRY (RID,VAL_D1,VAL_D2,VAL_D3) values (39,-812783.09,-1079712.302,395.454);
Insert into ENTRY (RID,VAL_D1,VAL_D2,VAL_D3) values (40,-812783.047,-1079712.353,394.932);
Insert into ENTRY (RID,VAL_D1,VAL_D2,VAL_D3) values (41,-812783.039,-1079712.348,394.7);
Insert into ENTRY (RID,VAL_D1,VAL_D2,VAL_D3) values (42,-812783.058,-1079712.244,394.299);
Insert into ENTRY (RID,VAL_D1,VAL_D2,VAL_D3) values (43,-812782.795,-1079712.241,388.511);
Insert into ENTRY (RID,VAL_D1,VAL_D2,VAL_D3) values (44,-812782.951,-1079712.715,395.341);
Insert into ENTRY (RID,VAL_D1,VAL_D2,VAL_D3) values (45,-812782.871,-1079712.126,388.876);
Insert into ENTRY (RID,VAL_D1,VAL_D2,VAL_D3) values (46,-812782.851,-1079712.153,388.673);
Insert into ENTRY (RID,VAL_D1,VAL_D2,VAL_D3) values (47,-812783.088,-1079712.415,395.544);
Insert into ENTRY (RID,VAL_D1,VAL_D2,VAL_D3) values (48,-812783.036,-1079712.423,394.445);
Insert into ENTRY (RID,VAL_D1,VAL_D2,VAL_D3) values (49,-812782.812,-1079712.287,388.091);
Insert into ENTRY (RID,VAL_D1,VAL_D2,VAL_D3) values (50,-812782.988,-1079712.771,395.471);
Insert into ENTRY (RID,VAL_D1,VAL_D2,VAL_D3) values (51,-812783.007,-1079712.65,394.917);
Insert into ENTRY (RID,VAL_D1,VAL_D2,VAL_D3) values (52,-812783.028,-1079712.554,394.606);
Insert into ENTRY (RID,VAL_D1,VAL_D2,VAL_D3) values (53,-812783.125,-1079712.233,394.138);
Insert into ENTRY (RID,VAL_D1,VAL_D2,VAL_D3) values (54,-812783.011,-1079712.667,394.702);
Insert into ENTRY (RID,VAL_D1,VAL_D2,VAL_D3) values (55,-812783.006,-1079712.762,395.017);
Insert into ENTRY (RID,VAL_D1,VAL_D2,VAL_D3) values (56,-812783.011,-1079712.811,395.158);
Insert into ENTRY (RID,VAL_D1,VAL_D2,VAL_D3) values (57,-812782.795,-1079712.52,388.086);
Insert into ENTRY (RID,VAL_D1,VAL_D2,VAL_D3) values (58,-812783.136,-1079712.427,394.343);
Insert into ENTRY (RID,VAL_D1,VAL_D2,VAL_D3) values (59,-812783.104,-1079712.83,395.342);
Insert into ENTRY (RID,VAL_D1,VAL_D2,VAL_D3) values (60,-812783.163,-1079712.621,394.922);
Insert into ENTRY (RID,VAL_D1,VAL_D2,VAL_D3) values (61,-812782.854,-1079712.652,388.084);
Insert into ENTRY (RID,VAL_D1,VAL_D2,VAL_D3) values (62,-812783.145,-1079712.839,395.551);
Insert into ENTRY (RID,VAL_D1,VAL_D2,VAL_D3) values (63,-812783.037,-1079712.216,388.092);
Insert into ENTRY (RID,VAL_D1,VAL_D2,VAL_D3) values (64,-812783.195,-1079712.69,395.047);
Insert into ENTRY (RID,VAL_D1,VAL_D2,VAL_D3) values (65,-812782.955,-1079712.479,388.084);
Insert into ENTRY (RID,VAL_D1,VAL_D2,VAL_D3) values (66,-812783.19,-1079712.764,395.181);
Insert into ENTRY (RID,VAL_D1,VAL_D2,VAL_D3) values (67,-812783.294,-1079712.546,395.213);
Insert into ENTRY (RID,VAL_D1,VAL_D2,VAL_D3) values (68,-812783.367,-1079712.397,395.208);
Insert into ENTRY (RID,VAL_D1,VAL_D2,VAL_D3) values (69,-812783.428,-1079712.238,395.218);
Insert into ENTRY (RID,VAL_D1,VAL_D2,VAL_D3) values (70,-812783.046,-1079712.616,388.092);
Insert into ENTRY (RID,VAL_D1,VAL_D2,VAL_D3) values (71,-812783.551,-1079712.259,395.305);
Insert into ENTRY (RID,VAL_D1,VAL_D2,VAL_D3) values (72,-812783.216,-1079712.317,388.101);
Insert into ENTRY (RID,VAL_D1,VAL_D2,VAL_D3) values (73,-812783.313,-1079712.113,388.135);
Insert into ENTRY (RID,VAL_D1,VAL_D2,VAL_D3) values (74,-812783.685,-1079712.105,395.301);
Insert into ENTRY (RID,VAL_D1,VAL_D2,VAL_D3) values (75,-812783.431,-1079712.186,388.177);
Insert into ENTRY (RID,VAL_D1,VAL_D2,VAL_D3) values (76,-812783.233,-1079712.689,388.15);
Insert into ENTRY (RID,VAL_D1,VAL_D2,VAL_D3) values (77,-812783.543,-1079712.105,388.313);
Insert into ENTRY (RID,VAL_D1,VAL_D2,VAL_D3) values (78,-812783.507,-1079712.357,388.155);
Insert into ENTRY (RID,VAL_D1,VAL_D2,VAL_D3) values (79,-812783.601,-1079712.229,388.258);
Insert into ENTRY (RID,VAL_D1,VAL_D2,VAL_D3) values (80,-812783.806,-1079712.182,388.313);
Insert into ENTRY (RID,VAL_D1,VAL_D2,VAL_D3) values (81,-812783.49,-1079712.117,395.403);
Insert into ENTRY (RID,VAL_D1,VAL_D2,VAL_D3) values (82,-812783.339,-1079712.28,395.394);
Insert into ENTRY (RID,VAL_D1,VAL_D2,VAL_D3) values (83,-812783.066,-1079712.5,394.831);
Insert into ENTRY (RID,VAL_D1,VAL_D2,VAL_D3) values (84,-812783.128,-1079712.538,395.276);
Insert into ENTRY (RID,VAL_D1,VAL_D2,VAL_D3) values (85,-812783.082,-1079712.577,395.044);
Insert into ENTRY (RID,VAL_D1,VAL_D2,VAL_D3) values (86,-812783.267,-1079712.51,388.149);
Insert into ENTRY (RID,VAL_D1,VAL_D2,VAL_D3) values (87,-812783.21,-1079712.661,395.301);
Insert into ENTRY (RID,VAL_D1,VAL_D2,VAL_D3) values (88,-812783.2,-1079712.397,395.419);
Insert into ENTRY (RID,VAL_D1,VAL_D2,VAL_D3) values (89,-812783.209,-1079712.193,395.611);

Similar Messages

Installed the latest Java update today on my older iMac and now it won't boot up at all. 2007 model worked fine this morning, now disk first aid say boot blocks f'ed.

I am using an older mid 2007 imac 24 inch running snow leopard 10.6.8
I normally accept software update recs, and today when installing the security update to java, all went fine till restart, when I got the universal "NO" sign, the circle with the line through it and just spinning gray bars underneath.
Booted from system disks, ran first aid, said the boot block partitions or something like that needed updating but disk appears to be ok. Still not working.
Do you think Alsoft Disk Warrior will fix? I am running off external back up drive now.
Thanks for any help or advice. Apple as usual is as useless as tits on a bull, or a screen door on a submarine, pick your simile...

If your backup's up to date it might be less hassle to erase the internal and clone back from the backup. Don't allow the update next time it appears - you're not the only one having problems it would seem.
Note; the message "updating boot partitions" is a standard message that appears after a repair run. It won't go away and should be ignored.
Provided the message "The volume Macintosh HD Seems to be OK" in green has appeared, your disc fle system is fine.
Message was edited by: noondaywitch

How to fix this error? The startup disk cannot be partitioned or restored to a single partition.

Hey guys,
I am trying to install windows 7 ultimate 64 bit via bootcamp assistant. I open bootcamp assistant from utilities and i get the second window and try to click continue and i get a pop up, saying "The startup disk must be formatted as a single Mac OS Extneded (journaled) volume or already partitioned by Boot Camp Assistant for installing Windows." I looked around on the internet, i found that my internal HD must be set to OS Extended (Journaled). I went into disk utility and i clicked partition tab and the option was set to OS extended (journaled). Any ideas on how to overcome this error so i can install windows 7?

Error is:
1: common
2: misleading and poorly worded
3: space must be:
A: contiguous, that means unfragmented and in ONE section, not multiple
B: files cannot be loced, anchored or in such a manner as to prevent or block partition operation
C: to move, unlock and shuffle files requires booting from another drive or device
Shrink the HFS+ volume by as much or more than you need to set aside to use
If that does not,
Try iDefrag from another hard drive or by burning and using its own CD that is just for consolidating free space
Clone your system (should have backups already, clone is just bootable)
Erase and restore from clone - SuperDuper does consolidate files and free space and result in unfragmented (99% success rate)
None of which has to do iwth what that error message says. This error has been almost a daily threat topic - has gotten less but has not "gone away."

Arch PPC issue with creating bootstrap partition

On second thought, I'm doing good.
Last edited by Kebertx (2012-01-13 22:35:32)

On second thought, I'm doing good.
EDIT: Didn't want to be a help vampire. Something I recently learned about, and felt bad to identify as.
So, in case anyone is trying to install Arch on a PowerMac G4, and messed up around the mac-fdisk step, I stumbled upon a thing that you shouldn't do.
After you hit i to initialize the partition map
DON'T hit p too early to print the table. You're supposed to enter the full block size. Doing this causes fdisk to believe you are setting up a 4 block partition. The bootstrap partition has to be 64 blocks, so that will just be completely non-working.
A very simple foolhardy mistake. Forgive me forum, I did not see. That little letter p in the wrong line... nightmarish, now that I look back on it.
The Wiki will lead you well until you get to the kernel.
# type name length base
( size ) system
/dev/hda1 Apple_partition_map Apple 63 @ 1
( 31.5k) Partition map
/dev/hda2 Apple_Bootstrap bootstrap 1600 @ 64
(800.0k) NewWorld bootblock
/dev/hda3 Apple_UNIX_SVR2 root 31457280 @ 1664
( 15.0G) Linux native
/dev/hda4 Apple_UNIX_SVR2 swap 3072000 @
31458944 ( 1.5G) Linux swap
/dev/hda5 Apple_UNIX_SVR2 home 121770544 @
34530944 ( 58.1G) Linux native
Block size=512, Number of Blocks=156301488
DeviceType=0x0, DeviceId=0x0
For the kernel the wiki is giving you something outdated. When you're installing the base, do this:
pacman -r /mnt -S base --ignore linux-pmac64 --ignore linux-pmac
And installing the kernel is like this:
pacman -r /mnt -S linux-pmac
pacman -r /mnt -S linux-pmac64
^If you are using x64.^
Am I a helpful community member now?

How to Serve LIDAR (SDO_PC) from LAS_Importer?

Hi,
Using the LAS-Importer from Oracle, I have loaded a LAS file and further created the SDO_PC object that breaks it into 2D block extents.
I am now wondering what the best way would be to serve this data for use by an external viewer (preferably as GML so it may be easily manipulated)?
I know an SDO_PC_PKG.TO_GEOMETRY() call will return a 3D multi-point geometry however it is preferable not to give the external viewer direct access to the database or have to use a JDBC.
Does the WebLogic WFS serve up GML for SDO_PC blocks? (The data either in the BASE or BLKTAB# tables)?
I am currently using GeoServer to serve up my 2D geometries but I don't know how it would handle 3D (or the representation of the point cloud created by the LAS-Importer).
Thanks for your help!

Currently there is no standard way to serve the SDO_PC data via a WFS or GML.
You have to write custom code to do that. For example, you can create a view that serves the data as 2D geometries
using the sdo_pc.to_geometry function and use that view as a feature layer.
siva

9anonymous blocked when it shouldn't be

Hi,
I'm trying to setup a way to block specific incoming calls on our CUCM 9 platform. I've got it so that it blocks specific numbers and allows through all other calls providing the caller has calling line ID enabled. Trouble is it's also blocking all calls from unknown \ withheld numbers. We're using SIP trunks to connect to the PSTN and the calling line ID for all withheld numbers is sent down the trunk is "9anonymous".
RTMT reports Termination Cause Code (1) Unallocated (unassigned) number for the failed withheld calls
I've setup the call blocking following these instructions:
https://supportforums.cisco.com/document/71966/blocking-calls-based-calling-party-id
http://www.netcraftsmen.com/cisco-cucm-blocking-calls-by-calling-party-number-id/
The CSS setting on the Inbound Settings of the SIP trunk uses "CS-SIP-INBOUND"
The Partition PA-SIP-INBOUND is in this CSS with two Translation Patterns:
and
<null> (no title)
Both have the "Route Next Hop by Calling Party Number" option enabled
Both are configured to use CS-SIP-INBOUND-BLOCKED
The CSS CS-SIP-INBOUND-BLOCKED has one Partition PA-SIP-INBOUND-BLOCKED
With two Translation Patterns assigned exactly as above but with RNHCPN disabled and using the standard CSS for use for national call access.
I've then created Translation Patterns for the numbers to be blocked and assigned them to the PA-SIP-INBOUND-BLOCKED partition
I had though that the withheld numbers would be handled by the <null> Translation Patterns but that doesn't seem to be the case and I can't create a TP called "9anonymous" as a workaround either.
Any ideas?
Thanks!

I have been playing around to try and tie down exactly where the problem is occuring.
It is due to the fact that no data is being passed to the smartform when print is pressed, only when print preview is pressed.
I have created a test smartform that displays a single field (in this case caufvd-aufnr) to check the fact.
Here is the print processing ABAP I am using:
[code]
*& Report ZSJM_SMARTFORMTEST                                          *
REPORT zsjm_smartformtest                      .
DATA: value(10) TYPE c,
      fm_name TYPE rs38l_fnam,
      output TYPE ssfcompop,
      user TYPE tdbool.
INITIALIZATION                                                       *
INITIALIZATION.
INCLUDE riprid01.   "Contains the tables and data declarations
START-OF-SELECTION                                                   *
START-OF-SELECTION.
$$
PERFORM print_form.
$$
*&      Form PRINT_FORM
     Main form printing routine
FORM print_form.
value = 'TESTSTRING'.
output-tdnewid = 'X'.
output-tdimmed = 'X'.
user = SPACE.
CALL FUNCTION 'SSF_FUNCTION_MODULE_NAME'
    EXPORTING
      formname = 'ZSJMTEST'
    IMPORTING
      fm_name = fm_name.
CALL FUNCTION fm_name
    EXPORTING
      data           = caufvd
      value          = value
      output_options = output
      user_settings = user.
ENDFORM.                    "PRINT_FORM[/code]
Does anyone have any ideas why this isn't working?
It seems "caufvd" isn't getting sent the data.
Message was edited by: Stuart Mayor

Bad PBR sig and dual booting with Windows

This site's menu config is too difficult for me...
fyi.
=>
Below is the cases that happened in my environment
when installing Solaris 8 Operating Environment, Intel Platform Edition
Some will help you, and some may be just for your thinking.
Bad PBR sig
You know what it means?
I don't know.
If you know, let me know please...
@ Case 1
My Seagate ST39236LW 9.2GB HARD DISK fdisk info
Total disk size is 14342 cylinders
Cylinder size is 1251 (512 byte) blocks
Partition Status Type Start End Length %
========= ====== ============ ===== === ====== ===
1 IFS:NTFS 0 7165 7166 50
2 Active x86 boot 7166 7182 17 0
3 Solaris 7183 14341 7159 50
(I use cylinder number to partition hard disk. Why?
When I use % and insert 1% to partition 2 then
fdisk makes start cylinder 7155.
It overlays with partition 1's end cylinder number.
So fdisk save(menu no 4) fails...
because the partition 1's start cylinder number is 0 ?)
After rebooting, bizarre Bad PBR sig, and my system dies...
So I boots my PC with Windows(or Dos) booting diskette.
A> fdisk
First Hard Disk partition info
1 NTFS 4377 50%
2 NON-DOS 10 0%
3 A NON-DOS 10 0% <= Solaris created x86 boot
4 NON-DOS 4363 0%
Solaris created extra X86 boot partition 3 and made it active.
But partition 3 could not boot...
I made partition 2 active from dos fdisk menu,
and pc boots well.
After rebooting, my disk partition info is like this
Total disk size is 14342 cylinders
Cylinder size is 1251 (512 byte) blocks
Partition Status Type Start End Length %
========= ====== ============ ===== === ====== ===
1 IFS:NTFS 0 7165 7166 50
2 Active x86 boot 7166 7182 17 0
3 x86 boot 7183 7199 17 0
4 Solaris 7200 14341 7142 50
Then after installation?
Partition Status Type Start End Length %
========= ====== ============ ===== === ====== ===
1 IFS:NTFS 0 7165 7166 50
2 Active x86 boot 7165 7181 17 0
3 Solaris 7200 14341 7142 50
Partition 2 and 3 changed...
Where did partition 3 go???
Just deleted?
Then why partition 2 Start cylinder changed?
@ Case 2.
Another queer thing....
Total disk size is 14342 cylinders
Cylinder size is 1251 (512 byte) blocks
Partition Status Type Start End Length %
========= ====== ============ ===== === ====== ===
1 IFS:NTFS 0 7165 7166 50
2 Active Solaris 7166 14341 7176 50
In Solaris x86 format fdisk menu,
if I've allocated remaining disk space all to Solaris(without x86 boot),
then Solaris also makes x86 boot partition(size 10MB), reboots well.
But install fails due to not enough free disk space
when install begins slicing Solaris partition.
error log says
Installing 32 Bit Solaris Packages
- Configuring boot device
- Using disk(c0t0d0) for "rootdisk"
- Deleting x86 boot fdisk partition (c0t0d0)
- Creating x86 boot fdisk partition (c0t0d0)
ERROR:Not enough free space to create x86 Boot fdisk partition(c0t0d0)
Why does Solaris delete and create x86 boot partition?
Why did it exist?
Case 3.
If I've fdisked like this, what will happen???
Total disk size is 14342 cylinders
Cylinder size is 1251 (512 byte) blocks
Partition Status Type Start End Length %
========= ====== ============ ===== === ====== ===
1

BAD PBR SIG message comes from your BIOS - no partition boot record.
Sorry but it's not clear what else is going on - might be worth running a ODS based fdisk to clear the disk before installing Solaris?

Shared SO's and Load Balancing

On Wed, 21 Jan 1998 17:24:33 -0000, Richard Stobart wrote:
Dale,
If SHARED is true in a Service Object then the Service Object is not
re-entrant (because many clients are sharing its variables and therefore is
not multitasked (Funny logical naming if you ask me)). I got a lot of replies correcting me on what SHARED means! I do know
what SHARED means, I just phrased it backwards in my post. Excuse me
while I smack myself upside the head. :)
All replicates of a
load balanced partition are not re-entrant and thus equivalent to SHARED =
true. The advantage of load balancing is that the replicates can be
distributed over machines and thus the load is balanced. What I fail to understand is this: If you have a non-SHARED SO all by
itself in a partition which is not load-balanced, it will be
re-rentrant and multiple users can call it at the same time. But as
soon as you load-balance it, all of a sudden it behaves as if it were
SHARED. Why? I don't understand the technical limitations that impose
this, nor do I understand the advantage. For example, let's say that I
have 50 concurrent users of the SO I described above. It's in a
non-load-balanced partition, so all 50 users can access it at the same
time without any problem. Now let's say my server is a little
stressed, so I decide I want to load-balance my SO and have two
replicates, one on the original server and one on a second server. But
now that I've load-balanced it, the partitions act as if they're SHARED
and my 50 concurrent users are going to be lining up in queues and
suffering from horrible response times. How is this advantageous?
================================================
Dale V. Georg
Systems Analyst
Indus Consultancy Services
[email protected]
================================================

Dale,
The argument for load balancing services falls into two basic categories:
1. The service is blocking. That is, it is either not thread safe, not
signal tolerant, or not re-entrant. Most database libraries are the most
common example of this. Any partition that contains a non-multi-threaded
DB library will block the entire partition. Thus, you MUST load balance.
2. You want to spread the load across multiple servers. This is a tricky
one - you really have to do load testing to see if you're getting the
benefits you think you are.
Load balancing vs. multi-threading is a pretty hot topic among all of the
clients I visit. On a machine with native or certified POSIX threads and
multiple CPUs, you will certainly gain significant performance by not
load-balancing a non-blocking partition. Compare this with shared and/or
transactional services within a partition, non-native or non-POSIX thread
partitions, and machines with one CPU, and you have yourself quite a pot of
fish soup. Add another machine with differing properties, and the effects
can be exponential.
Then, there is also the notion that load balanced services are
intrinsically single threaded, which is not true. They can, and often do,
act as single threaded services because of the router. But it doesn't
imply that either the router, nor the partitions it routes, are necessarily
single threaded.
Don
At 07:38 PM 1/21/98, Dale V. Georg wrote:
On Wed, 21 Jan 1998 17:24:33 -0000, Richard Stobart wrote:
Dale,
If SHARED is true in a Service Object then the Service Object is not
re-entrant (because many clients are sharing its variables and therefore is
not multitasked (Funny logical naming if you ask me)). I got a lot of replies correcting me on what SHARED means! I do know
what SHARED means, I just phrased it backwards in my post. Excuse me
while I smack myself upside the head. :)
All replicates of a
load balanced partition are not re-entrant and thus equivalent to SHARED =
true. The advantage of load balancing is that the replicates can be
distributed over machines and thus the load is balanced. What I fail to understand is this: If you have a non-SHARED SO all by
itself in a partition which is not load-balanced, it will be
re-rentrant and multiple users can call it at the same time. But as
soon as you load-balance it, all of a sudden it behaves as if it were
SHARED. Why? I don't understand the technical limitations that impose
this, nor do I understand the advantage. For example, let's say that I
have 50 concurrent users of the SO I described above. It's in a
non-load-balanced partition, so all 50 users can access it at the same
time without any problem. Now let's say my server is a little
stressed, so I decide I want to load-balance my SO and have two
replicates, one on the original server and one on a second server. But
now that I've load-balanced it, the partitions act as if they're SHARED
and my 50 concurrent users are going to be lining up in queues and
suffering from horrible response times. How is this advantageous?
================================================
Dale V. Georg
Systems Analyst
Indus Consultancy Services
[email protected]
================================================
============================================
Don Nelson
Regional Consulting Manager - Rocky Mountain Region
Forte Software, Inc.
Denver, CO
Phone: 303-265-7709
Corporate voice mail: 510-986-3810
aka: [email protected]
============================================
"We tigers prefer to inflict excitement on others." - Hobbes

Bloom Filter

I'd like to implement a distributed bloom filter using Coherence.
Bloom filter: it is an array of bits (true/false). The size of the array m is determined using the number of keys n we would like to encode. For example, for a given n=16 keys, the size of the bit array is 16*(some-optimality-factor) = 128.
The filter uses k hash functions. We hash each given key using our k hash functions h1,h2,..,hk into the bit array locations i1,i2,...,ik where each i is between 0 and m-1.
The reason I am using the bloom filter is to save space. Say keys are Long, then instead of using n*64 bits, I'd like to use m bits.(less than n*64 bits)
How can I implement this structure efficiently using Coherence?
Message was edited by:
bulut

Let me take a shot a rephrasing/simplifying the question:
There's two important functions that need to be taken care of when implementing a distributed bloom filter:
1- There is the need to distribute a (potentially) very large bit vector.
2- There is the need to apply several accesses (i.e., check several bits) in order to get a single response. The response is a yes/no (i.e., the logical bitand of the bits accesses).
Now suggestions:
a) To solve 1 one, the first thing that comes to mind is to break the bit vector into smaller bit vectors that are keyed by a "bit block" index. For example, if my bitvector contains 800 bits, I may break it up in blocks of 80bits. In that case I could have a distributed map with 10 entries each of them containing an bit vector of 80bits (ie., each entry can contain a byte array of size 10) and the key of each entry can correspond to the offset of its first bit. Now, the question that bulut asked is: Is there a better way to represent a bit vector within a distributed map?
b) in connection to the previous question comes the fact of how to index the bits...if adopting the block partitioning strategy that I just describe, what's the most efficient way to index the bits (and not just the keys that refer to bitblocks)?
c) Finally there's the multiple access question. Since additions and lookups to the filter (i.e., bitarray) are done in groups, it would be highly beneficial to perform them in parallel.
An addition to the filter corresponds to setting k bits in the array in one shot. This would map into probably very distant bits in the array (therefore it does not map to change a single bitblock). That probably calls for using either the invocable map or aggregator functionality...although I'm not much familiar with it so I'm not sure.
In terms of a lookup, there's also an interesting difference from normal access. And that is that given a set of bit offsets, we want to get a yes/no answer (corresponding to the logical and of the values existing in the array). I guess this also has a strong aggregator smell...
Well I hope I clarified more than anything else.
Cheers,
Josep M.

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

Correcting a bad block on ext4 and with GTP partition table

Hello,
I ran a SMART offline test today which came back as a bad block:
# 1 Extended offline Completed: read failure 30% 8363 3212759896
This is my first run-in with a bad block, and since these drives are big and relatively new, I want to be proactive and fix any problems as they arise. Here is my setup:
* I have 2x 2TB HDDs of same make and model, with the device link being /dev/sdc and /dev/sdd. /dev/sdc is the one with the error.
* These two disks are linked via a Linux RAID 1 array under /dev/md0 which is then mounted on /storage.
* Both drives have only 1 partition under a GUID Partition Table (GPT)
I've looked around to try to find info on fixing bad blocks, and I came across this: smartmontools.sourceforge.net/badblockhowto.html
However, it seems to be out-dated and geared for tools like fdisk (which I cannot use for GPT) and filesystems ext2/3 (although, due to the backwards compatibility, I'm sure it works with ext4 as well), and a lot fo the commands gives things like "Couldn't find valid filesystem superblock."
Can someone point me in the right direction as to how I can fix this issue?
EDIT:
My noob is showing. I got the commands above to work, and when I check to see which file is using the bad block it shows this (after all the calculations involved, the block was 401594731):
debugfs: icheck 401594731
Block Inode number
401594000 <block not found>
So i'm assuming that there isn't a file assigned to it (empty space?). But then, when I use dd to read from it, it seems to read just fine:
sudo dd if=/dev/md0 of=my.block skip=401594731 bs=4096 count=1
1+0 records in
1+0 records out
4096 bytes (4.1 kB) copied, 0.0222587 s, 184 kB/s
I think it's able to read it since the other disk in the RAID1 array doesn't have the bad block. But I just want to make absolutely sure that there is no file assigned to that block before I nuke it. Given the above information, would it be safe to remove this block from service?
Last edited by XtrmGmr99 (2012-01-26 01:17:51)

Yes I think the block is not in use. You can do
debugfs: testb 401594731
which will state it clearly ("not in use" vs "marked in use")

I can't make a partition in a Macbook air, the disk is blocked

I have a macbook air with 10.8.2 and 60GB of memory. I want to make a partition to install linux ubuntu and the disk is blocked.

Click here and request assistance.
(82727)

Really still need EBS (Erase Block Size) for partitioning a SSD?

The Arch wiki mentions that when partitioning an SSD you need to align the partitions to the erase block size (see https://wiki.archlinux.org/index.php/Pa … ate_drives ). There are a lot of how-to-partition-an-ssd-under-linux which also mention this value, even an online calculater.
Those value are known for a lot of the serious models, among them also the Samsung 840 Pro and EVO. As I already asked in an older thread, I would like to know the value for the current model Samsung 850 Pro. Unfortunately Samsung Germany's support refuses to provide me with those values.
Therefore I ask myself, is it still necessary to align partititions to a multiple of the EBS, or is this unnecessary if the device supports TRIM?
Thanks!

Did you read the section immediately after the one you linked? https://wiki.archlinux.org/index.php/Pa … ng_tools_2
In past, proper alignment required manual calculation and intervention when partitioning. Many of the common partition tools now handle partition alignment automatically:
To verify a partition is aligned, query it using /usr/bin/blockdev as shown below, if a '0' is returned, the partition is aligned
Is that not sufficient for your purposes?
Last edited by 2ManyDogs (2014-11-04 18:55:37)

How would I fix a bad block on a partition?

I've been trying to resize a Western Digital 250GB drive that has Windows XP on the primary /dev/hda partition. PartitonMagic reports "Error 1529 while executing batch" & "Error 1529: Information mismatch in directory entry" I've read it up and the solution is supposed to be running "chkdsk /f"but I've run "chkdisk /r & /f" multiple times and I still get this error.
I also tried to partition form a gparted cd, it tells me that there is at least 1 bad block and it cannot continue. It suggested chkdsk and running ntfsresize with --bad-sectors. I did this with "ntfsresize -b -s182880MB /dev/sda1" it seemed to have worked but when I logged in to Windows I noticed that while my C: was resized to 182GB, no unallocated space was created. (Not sure if I missed a step in this process) So partition magic and other apps show a 250GB+ drive with no unallocated free space. While my C:\ shows up as 182GB.
I also tried Ultimate Boot Disk, with qtparted & simplyMephis liveCD with qtparted. UBD just said there were errors, simplyMephis said there was at least 1 bad block on the drive. I tried running badblocks commands from Mephis but it looked like it would take days to complete at the speed it was doing it.
Any more ideas? Has anyone else come across these problems?

You may try to launch a "cfdisk" from a live CD to see if the partitions are set up correctly and maybe write a proper partition table. Be warned, this is a formatting tool, so you can loose all your data if manipulated incorrectly.
Moreover, partitionning a drive while the system uses it is not a good idea. Always prefer doing this from a live system (that uses only RAM).

Anyone using an SSD? did you align partitions to erase blocks?

I'm waiting on the 2nd gen Intel SSDs to copy my / and /home to the faster I/O device. In the meantime, I'm reading up on these things and have found numerous sources that suggest aligning partitions on SSD's to the erase block of the device. I found two major sources detailing the process. This one shows a setup using parted and explains the process.
I'm just posting to solicit feedback from the community on this issue. Does Aloisio have it right in that blog post?

Thanks for the link... most of that went over my head though. I'm not too sure about the whole boot 'tricky offset' as you described it though
My partition scheme for the 80 gig ssd will be pretty simplistic:
20 gigs of NTFS as partition #1
15 gigs of ext4 as partition #2
200 meg of ext3 for /boot as partition #3
rest of the drive for /home as partition #4
I'll keep /var and /data partitions on my HDD.
Glad to hear more comments about this so I can do it right the first time
Last edited by graysky (2009-08-14 21:35:29)

SDO_PC blocks partition

Similar Messages

Maybe you are looking for