IGS create bitmap imagine

Hi
I'm trying to send data to create a bitmap graph image.
We are on 6.20, so I only have class : cl_igs_chart available to me. I know that with class cl_igs_chart_engine in 6.40 you can produce bitmaps and convert with images with CL_IGS_IMAGE_CONVERTER but both these classes are not avaiable to me.
How can I create a bitmap image graph in class : cl_igs_chart or is there another method ?
Also I does anyone know how i can create a line chart instead of a bar chart using the class cl_igs_chart / cl_igs_chart_engine
Thanks

no, the loader class is a displayobject so you can use the
draw method of the bitmapdata class to "draw" your loader to a
bitmapdata object. just be sure to wait until loading is complete
before you do that.

Similar Messages

Bad performance "CREATE BITMAP INDEX"

Hi,
i just create a bitmap index on a fact table with ~90.000.000 entries. The indexed table is the artice dimension with a cardinality of about 900.000 articles.
The process is running since 24 hours with a parallel degree of 4, 3 slaves finished their work, only one is still collecting/sorting. PGA_AGGREGATE_TARGET is 4 GB.
Oralce has allocated a temporary segment in the temp. tablespace which has a size of 760 MB up to now.
Any idea how to speed up the process except increasing the degree for parallel query ?
Is there a space limit for processes allocating main memory in the PGA. Or is it absolutely impossible to setup Oracle memory for workareas in a way, so that such a big bitmap can be created in main memory ? I dont want to switch back to the 8i features CREATE_BITMAP_AREA_SIZE,...
Any hint is welcome, thx in advance...
Paul

Hello,
Please check <Bug:3048661>
Hdr: 3048661 9.2.0.3.0 RDBMS 9.2.0.3.0 RAM INDEX PRODID-5 PORTID-23
Abstract: CREATE BITMAP INDEXES TAKES LONGER IN 9203 WHEN PGA => 2GB
Thanks
Ashish

Importing SWF creates bitmap and graphic

I've created my user interface in Photoshop >
opened file in ImageReady and exported document as SWF for my Flash
8 pro. When the SWF is imported to Library in Flash, the library
gets a bitmap AND a graphic of each image.
Can someone explain why?
Which should I use on the stage?
Do I need to keep both library items?
*Confused*

B_Milou,
> I've created my user interface in Photoshop > opened
file in
> ImageReady and exported document as SWF for my Flash
> 8 pro.
Okay.
> When the SWF is imported to Library in Flash, the
library gets
> a bitmap AND a graphic of each image.
Photoshop is a raster image editor. It has some vector
capability, but
generally speaking, it creates bitmaps. It, coupled with
ImageReady, may
have the capability of exporting those bitmaps as SWF files,
but those SWFs
are merely "wrappers" for a bunch of bimap files.
> Which should I use on the stage?
If you want to tween these assets, you'll likely want the
symbols (not
the image files) on the Stage.
> Do I need to keep both library items?
Yes. The symbols merely hold the image files. If you delete
the image
files, the symbols will be empty.
David Stiller
Adobe Community Expert
Dev blog,
http://www.quip.net/blog/
"Luck is the residue of good design."

Aperture 3 bug:Failed to create bitmap context color transform

*Aperture 3 error*: Aperture[2000] <Error> Failed to create bitmap context color transform
Aperture[2000] <Error> CGBitmapContextCreateWithData: failed to create delegate
Using Aperture 3.03 and Mac OS 10.6.4, all updates included.
This is the Console Message indicating the bug where Aperture 3.x cannot display in its viewer an image with an *embedded color profile*. These images (regardless whether tiff or jpegs) were displayed without problems in Aperture 2.x and do not pose any problems with Preview, Photoshop or Graphic Converter. If one converts the color profile to lets say ProPhoto or sRGB, Aperture works -
but this is no solution as colors are different then.
Is there any clue - based on the console message above - where the problem might be? The bug can be reproduced on different Mac Models with Aperture 3.x and vanishes with Aperture 2.x
is not dependen

Dear DLScreative,
please let us not fight over words - fact is, that with at least 2 totally different users and 4 different Mac computers Aperture 3.x behaves totally different (i.e. cannot display these images) than Aperture 2.x. The special color profile is embedded because 15.000 images were scanned with a Nikon LS5000
scanner. I don't know how to upload this color profile (which has been tested to be correct) to this
forum. Would you care if I sent you an E-Mail with the special profile attached so you could yourself
try and see?
Regards,

Error while attempting to create bitmap index

I get the error below while creating a bitmap index on a table in SQL Developer.
How do a go about enabling this feature? I looked on Tools | Preferences menu and didn't see anything.
Using Version 1.0.0.14.67
>>>
Error starting at line 1 in command:
CREATE BITMAP INDEX "SYSTEM"."PUB_SRC_INDX_0197_US4" ON "SYSTEM"."PUB_SRC_TBL_0197_US" ("STATUS_ID")
Error report:
SQL Error: ORA-00439: feature not enabled: Bit-mapped indexes
>>>
Thanks

Nevermind.. I found it on google. You must have an SE version of Oracle which does not support Bitmapped Indexes. You will have to use another index type.

Issue with creating bitmap image data for Format8bppIndexed and Format4bppIndexed

We are using below method to convert byte array into bitmap . we have successfully converted 16,24,32 etc. Pixel formats but we are facing issue while converting 4 and 8 pixel
formats image is rendering in blur format and image starting and ending positions are changed.
<summary>
/// Converting the raw data into bitmap
</summary>
<param name="buffer">Byte array of the image rawdata</param>
<param name="nWidth">Image width</param>
<param name="nHeight">Image height</param>
<param name="nBitCount">Image Pixel format</param>
<returns></returns>
internal
Bitmap ConvertRawDataToBitMap(byte[]
buffer, int nWidth,
int nHeight,
int nBitCount,PDIB
pDIB=null)
Size imageSize =
new
Size(nWidth, nHeight);
PixelFormat imagePixelFormat = GetPixelFormat(nBitCount);
Bitmap bitmap =
new
Bitmap(imageSize.Width, imageSize.Height, imagePixelFormat);
Rectangle wholeBitmap =
new
Rectangle(0, 0, bitmap.Width, bitmap.Height);
BitmapData bitmapData = bitmap.LockBits(wholeBitmap,
ImageLockMode.WriteOnly, imagePixelFormat);
//Marshal.Copy(buffer, 0, bitmapData.Scan0, buffer.Length);
Marshal.Copy(buffer, 0, bitmapData.Scan0, bitmapData.Stride * bitmap.Height);
bitmap.UnlockBits(bitmapData);
bitmap.RotateFlip(RotateFlipType.Rotate180FlipX);
return bitmap;
<summary>
/// Returns the pixel format from given bit count.
</summary>
<param name="nPixelBitCount">Pixel bit count example 4 or 8 or 16 or 24 ..etc</param>
<returns></returns>
private
PixelFormat GetPixelFormat(int
nPixelBitCount)
PixelFormat pixelFormat =
PixelFormat.Undefined;
switch (nPixelBitCount)
case 4:
pixelFormat =
PixelFormat.Format4bppIndexed;
break;
case 8:
pixelFormat =
PixelFormat.Format8bppIndexed;
break;
case 16:
pixelFormat =
PixelFormat.Format16bppRgb555;
break;
case 24:
pixelFormat =
PixelFormat.Format24bppRgb;
break;
case 32:
pixelFormat =
PixelFormat.Format32bppRgb;
break;
case 48:
pixelFormat =
PixelFormat.Format48bppRgb;
break;
case 64:
pixelFormat =
PixelFormat.Format64bppArgb;
break;
default:
pixelFormat =
PixelFormat.Undefined;
break;
return pixelFormat;
below is the converted image for 8 pixelformat
below is the Actual image
Please help me to find the solution.
Thanks in Advance,
Madhava Reddy and Madhu

Hi ,
We got below errors in the screen shots inserted.
MemoryStream msEVPict1 = new MemoryStream(buffer);
EVPict.pDIB.ImageBitmap = new Bitmap(msEVPict1);
MemoryStream
ms1 = new
MemoryStream(buffer);
System.Drawing.Image
img = Image
.FromStream(ms1);
Thanks,
Madhu & Madhav

Unable to create a bitmap index

Hi,
I want to create a bitmap index on one of the colums on a table. I fired following query and it failed.
SQL> CREATE BITMAP INDEX TRANS_N_BITMAPIDX_VEH_PLATFORM ON TRANSACTION_NEW(VEH_PLATFORM) LOCAL;
Error starting at line 2 in command:
CREATE BITMAP INDEX TRANS_N_BITMAPIDX_VEH_PLATFORM ON TRANSACTION_NEW(VEH_PLATFORM) LOCAL
Error at Command Line:2 Column:70
Error report:
SQL Error: ORA-01408: such column list already indexed
01408. 00000 - "such column list already indexed"
*Cause:
*Action:I found there is a combined NORMAL index with VEH_PLATFORM column called ‘IDX$$_30AA00021’. It has following columns
•     VEH_PLATFORM
•     VEH_MODEL
•     MODL_YR_NBR
•     VEH_MAKE
•     TXN_PROCS_DT
But I was able to create bitmap index on VEH_MODEL,MODL_YR_NBR and VEH_MAKE columns without any error.
Why does it error out for VEH_PLATFORM column?
Regards,
Sam

Hi,
I am sure that BITMAP index is only created for
VEH_MAKE
VEH_MODEL
MODL_YR_NBR
BUILD_REGION
VEH_LINE_SERIES
TRANS_CTG_ID
and not for VEH_PLATFORM.
SQL> SELECT * FROM USER_INDEXES WHERE INDEX_TYPE='BITMAP' AND TABLE_NAME='TRANSACTION_NEW';
INDEX_NAME                     INDEX_TYPE                  TABLE_OWNER                    TABLE_NAME                     TABLE_TYPE UNIQUENESS COMPRESSION PREFIX_LENGTH          TABLESPACE_NAME                INI_TRANS              MAX_TRANS              INITIAL_EXTENT         NEXT_EXTENT            MIN_EXTENTS            MAX_EXTENTS            PCT_INCREASE           PCT_THRESHOLD          INCLUDE_COLUMN         FREELISTS              FREELIST_GROUPS        PCT_FREE               LOGGING BLEVEL                 LEAF_BLOCKS            DISTINCT_KEYS          AVG_LEAF_BLOCKS_PER_KEY AVG_DATA_BLOCKS_PER_KEY CLUSTERING_FACTOR      STATUS   NUM_ROWS               SAMPLE_SIZE            LAST_ANALYZED             DEGREE                                   INSTANCES                                PARTITIONED TEMPORARY GENERATED SECONDARY BUFFER_POOL FLASH_CACHE CELL_FLASH_CACHE USER_STATS DURATION        PCT_DIRECT_ACCESS      ITYP_OWNER                     ITYP_NAME                      PARAMETERS                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               GLOBAL_STATS DOMIDX_STATUS DOMIDX_OPSTATUS FUNCIDX_STATUS JOIN_INDEX IOT_REDUNDANT_PKEY_ELIM DROPPED VISIBILITY DOMIDX_MANAGEMENT SEGMENT_CREATED
TRANS_N_BITMAPIDX_MAKE         BITMAP                      VISUAL                         TRANSACTION_NEW                TABLE       NONUNIQUE DISABLED                                                                                                                                                                                                                                                                                                                                                      2                      6102                   20                     305                     611                     12226                  N/A      12226                  2208                   11-MAY-11                 1                                        1                                        YES         N         N         N         DEFAULT     DEFAULT     DEFAULT          NO                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       YES                                                       NO         NO                      NO      VISIBLE                      N/A
TRANS_N_BITMAPIDX_MODEL        BITMAP                      VISUAL                         TRANSACTION_NEW                TABLE       NONUNIQUE DISABLED                                                                                                                                                                                                                                                                                                                                                      2                      11284                  158                    71                      144                     22813                  N/A      22813                  2321                   11-MAY-11                 1                                        1                                        YES         N         N         N         DEFAULT     DEFAULT     DEFAULT          NO                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       YES                                                       NO         NO                      NO      VISIBLE                      N/A
TRANS_N_BITMAPIDX_BUILD_REGION BITMAP                      VISUAL                         TRANSACTION_NEW                TABLE       NONUNIQUE DISABLED                                                                                                                                                                                                                                                                                                                                                      2                      2911                   5                      582                     1161                    5808                   N/A      5808                   5808                   11-MAY-11                 1                                        1                                        YES         N         N         N         DEFAULT     DEFAULT     DEFAULT          NO                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       YES                                                       NO         NO                      NO      VISIBLE                      N/A
TRANS_N_BITMAPIDX_MODL_YR_NBR BITMAP                      VISUAL                         TRANSACTION_NEW                TABLE       NONUNIQUE DISABLED                                                                                                                                                                                                                                                                                                                                                      2                      2911                   5                      582                     1161                    5808                   N/A      5808                   5808                   11-MAY-11                 1                                        1                                        YES         N         N         N         DEFAULT     DEFAULT     DEFAULT          NO                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       YES                                                       NO         NO                      NO      VISIBLE                      N/A
TRANS_N_BITMAPIDX_TRANS_CTG_ID BITMAP                      VISUAL                         TRANSACTION_NEW                TABLE       NONUNIQUE DISABLED                                                                                                                                                                                                                                                                                                                                                      2                      7547                   43                     175                     359                     15457                  N/A      15457                  2345                   11-MAY-11                 1                                        1                                        YES         N         N         N         DEFAULT     DEFAULT     DEFAULT          NO                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       YES                                                       NO         NO                      NO      VISIBLE                      N/A
TRANS_N_BITMAPIDX_VEH_LINE_S   BITMAP                      VISUAL                         TRANSACTION_NEW                TABLE       NONUNIQUE DISABLED                                                                                                                                                                                                                                                                                                                                                      2                      10581                  253                    41                      84                      21477                  N/A      21477                  2247                   11-MAY-11                 1                                        1                                        YES         N         N         N         DEFAULT     DEFAULT     DEFAULT          NO                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       YES                                                       NO         NO                      NO      VISIBLE                      N/A
6 rows selectedRegards,
Sam

How can I create a local [b]bitmap[/b] index on a [b]list-partitionintable?

Hello there,
Could anyone show me a sample code of How to create a local bitmap index on a list-partitioning table?
I tried some code such as
1):
CREATE BITMAP INDEX bix_CID
ON Sales(Customer_ID)
TABLESPACE INDX
STORAGE (INITIAL 32K NEXT 32K PCTINCREASE 0)
LOCAL NOLOGGING;
I can create the index with this statement, but when the status of the index is 'N/A' (means 'INVALID').
2):
CREATE BITMAP INDEX bix_ver ON Versions
(VERNUM) TABLESPACE INDX
LOCAL
(PARTITION par1
,PARTITION par2
,PARTITION par3
,PARTITION par4
,PARTITION par5
,PARTITION par6
,PARTITION par7
THen I get ORA-600 error.
Thanks a lot!
wendy

You are creating the index properly. When you create a local index, it creates same number of partitions as the partitions in the table which are tightly coupled to table partitions.
I guess you are checking the status of index in dba_indexes or user_indexes table. The status here could be misleading since this table gives status of non-partitioned indexes.
For partitioned indexes you should check for status in dba_ind_partitions or user_ind_partitions which gives status of each partition in index.
Chanda

Bitmaps

I have an ascii text (1s and 0s), representing 1-bit-per-pixel bitmap. I am
trying to convert this into an image that would be recognizable by windows
paint software. I made a custom header and appended the remainder of information
to it, creating one large array and passing this array to "write BMP file"
function. For some reason, the image get disthorted. I was wondering if I
should include some organizational markers (newlines) in the original array,
or what?? Any help would be appreciated.
FRH

Here's one reason. Try this:
create table t (c varchar2(1));
create bitmap index tbit on t (c);
insert into t values ('Y');
Don't commit yet.
In a different session enter the same insert statement:
insert into t values ('Y');
You'll see that the session hangs until the first one issues a commit.
A regular index won't do this.
Imagine hundreds of users inserting or updating this column and one of them does an update and goes to lunch before doing a commit.

Multi-column BITMAP index vs. multiple BITMAP indices?

Given the table (simple, made-up example):
CREATE TABLE applicant_diversity_info (
applicant_diversity_id NUMBER(12), PRIMARY KEY(applicant_diversity_id),
apply_date DATE,
ssn_salted_md5 RAW(16),
gender CHAR(1), CHECK ( (gender IS NULL OR gender IN ('M','F')) ),
racial_continent VARCHAR2(30), CHECK ( (racial_continent IS NULL
OR racial_continent IN ('Europe','Africa','America','Asia_Pacific')) ),
ethnic_supergroup VARCHAR2(30), CHECK ( (ethnic_supergroup IS NULL OR ethnic_supergroup IN ('Latin American','Other')) ),
hire_salary NUMBER(11,2),
hire_month DATE,
termination_salary NUMBER(11,2),
termination_month DATE,
termination_cause VARCHAR2(30), CHECK ( (termination_cause IS NULL
OR termination_cause IN ('Resigned','Leave of Absence','Laid Off','Performance','Cause')) )
Oracle (syntactically) allows me to create either one BITMAP index over all four small-cardinality columns
CREATE BITMAP INDEX applicant_diversity_diversity_idx ON applicant_diversity_info (
gender, racial_continent, ethnic_supergroup, termination_reason );
or four independent indexes
CREATE BITMAP INDEX applicant_diversity_gender_idx ON applicant_diversity_info ( gender );
CREATE BITMAP INDEX applicant_diversity_race_idx ON applicant_diversity_info ( raceial_continent );
etc.
What is the difference between the two approaches; is there any meaningful difference in disk-space between the one multi-colum index and the four single-column indexes? Does it make a difference in what the query-planner will consider?
And, if I define one multi-column BITMAP index, does the order of columns matter?

>
What is the difference between the two approaches; is there any meaningful difference in disk-space between the one multi-colum index and the four single-column indexes? Does it make a difference in what the query-planner will consider?
And, if I define one multi-column BITMAP index, does the order of columns matter?
>
You may want to read this two-part blog, that answers that exact question, by recognized expert Richard Foote
http://richardfoote.wordpress.com/2010/05/06/concatenated-bitmap-indexes-part-i-two-of-us/
http://richardfoote.wordpress.com/2010/05/12/concatenated-bitmap-indexes-part-ii-everybodys-got-to-learn-sometime/
As with many things Oracle the answer is 'it depends'.
In short the same considerations apply for a concatenated index whether it is bitmap or b-tree: 1) will the leading column usually be in the predicate and 2) will most or all of the index columns be specified in the queries.
Here are some quotes from part 1
>
Many of the same issues and factors in deciding to create a single, multi-column index vs. several, single column indexes apply to Bitmap indexes as they do with B-Tree indexes, although there are a number of key differences to consider as well.
Another thing to note regarding a concatenated Bitmap index is that the potential number of index entries is a product of distinct combinations of data of the indexed columns.
A concatenated Bitmap index can potentially use less or more space than corresponding single column indexes, it depends on the number of index entries that are derived and the distribution of the data with the table.
>
Here is the lead quote from part 2
>
The issues regarding whether to go for single column indexes vs. concatenated indexes are similar for Bitmap indexes as they are for B-Tree indexes.
It’s generally more efficient to access a concatenated index as it’s only the one index with less processing and less throwaway rowids/rows to contend with. However it’s more flexible to have single column indexes, especially for Bitmap indexes that are kinda designed to be used concurrently, as concatenated indexes are heavily dependant on the leading column being known in queries.

Partitioned IOT of Object Type - mapping table not allowed for bitmap index

Hi,
looks like a feature available for standard Partitioned IOTs is not supported for object based tables, namely the MAPPING TABLE construct to support secondary local bitmap indexes.
Can you confirm behaviour is as expected/documented?
If so, is a fix/enhancement to support mapping table for object-based Partitioned IOTs in the pipeline?
Results for partition-wise load using pipelined table function are very good, look-ups across tens of millions of rows are excellent.
Environment = Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - Production
OS = Oracle Enterprise Linux Server release 5.2 (Carthage) 2.6.18 92.el5 (32-bit)
Here's the potted test-case...
1) First the non object based Partitioned IOT - data is range-partitioned across the alphabet
CREATE TABLE IOT_Table (
textData VARCHAR2(10),
numberData NUMBER(10,0),
CONSTRAINT IOT_Table_PK PRIMARY KEY(textData))
ORGANIZATION INDEX MAPPING TABLE PCTFREE 0 TABLESPACE Firewire
PARTITION BY RANGE (textData)
(PARTITION Text_Part_A VALUES LESS THAN ('B') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_B VALUES LESS THAN ('C') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_C VALUES LESS THAN ('D') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_D VALUES LESS THAN ('E') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_E VALUES LESS THAN ('F') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_F VALUES LESS THAN ('G') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_G VALUES LESS THAN ('H') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_H VALUES LESS THAN ('I') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_I VALUES LESS THAN ('J') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_J VALUES LESS THAN ('K') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_K VALUES LESS THAN ('L') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_L VALUES LESS THAN ('M') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_M VALUES LESS THAN ('N') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_N VALUES LESS THAN ('O') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_O VALUES LESS THAN ('P') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_P VALUES LESS THAN ('Q') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_Q VALUES LESS THAN ('R') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_R VALUES LESS THAN ('S') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_S VALUES LESS THAN ('T') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_T VALUES LESS THAN ('U') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_U VALUES LESS THAN ('V') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_V VALUES LESS THAN ('W') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_W VALUES LESS THAN ('X') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_X VALUES LESS THAN ('Y') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_Y VALUES LESS THAN ('Z') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_Z VALUES LESS THAN (MAXVALUE) PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0))
NOLOGGING PARALLEL -- FLASHBACK ARCHIVE IOT_Flashback_Data
SQL> table IOT_TABLE created.
2) Create the local secondary bitmap index utilising the underlying mapping table
CREATE BITMAP INDEX IOT_Table_BMI1 ON IOT_Table (numberData)
LOCAL STORAGE (INITIAL 1M PCTINCREASE 0 NEXT 512K) NOLOGGING PARALLEL;
SQL> bitmap index IOT_TABLE_BMI1 created.
3) Quick test to confirm all ok
SQL> INSERT INTO IOT_Table VALUES ('ABC123',100);
SQL> 1 rows inserted.
SQL> SELECT * FROM IOT_Table;
TEXTDATA NUMBERDATA
ABC123     100
4) Now create a minimal object type to use as the template for object table
CREATE TYPE IOT_type AS OBJECT
textData VARCHAR2(10 CHAR),
numberData NUMBER(10,0)
) FINAL
SQL> TYPE IOT_type compiled
5) Attempt to create an object-based range partitioned IOT, including MAPPING TABLE clause as per step (1)
CREATE TABLE IOTObj_Table OF IOT_type (textData PRIMARY KEY)
OBJECT IDENTIFIER IS PRIMARY KEY ORGANIZATION INDEX
MAPPING TABLE -- we'd like to use this feature to enable use of Bitmap Indexes...
PCTFREE 0 TABLESPACE Firewire
PARTITION BY RANGE (textData)
(PARTITION Text_Part_A VALUES LESS THAN ('B') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_B VALUES LESS THAN ('C') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_C VALUES LESS THAN ('D') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_D VALUES LESS THAN ('E') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_E VALUES LESS THAN ('F') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_F VALUES LESS THAN ('G') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_G VALUES LESS THAN ('H') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_H VALUES LESS THAN ('I') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_I VALUES LESS THAN ('J') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_J VALUES LESS THAN ('K') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_K VALUES LESS THAN ('L') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_L VALUES LESS THAN ('M') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_M VALUES LESS THAN ('N') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_N VALUES LESS THAN ('O') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_O VALUES LESS THAN ('P') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_P VALUES LESS THAN ('Q') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_Q VALUES LESS THAN ('R') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_R VALUES LESS THAN ('S') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_S VALUES LESS THAN ('T') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_T VALUES LESS THAN ('U') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_U VALUES LESS THAN ('V') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_V VALUES LESS THAN ('W') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_W VALUES LESS THAN ('X') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_X VALUES LESS THAN ('Y') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_Y VALUES LESS THAN ('Z') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_Z VALUES LESS THAN (MAXVALUE) PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0))
NOLOGGING PARALLEL -- FLASHBACK ARCHIVE IOT_Flashback_Data
This errors out with the following...
SQL Error: ORA-25182: feature not currently available for index-organized tables
25182. 00000 - "feature not currently available for index-organized tables"
*Cause:    An attempt was made to use one or more of the following feature(s) not
currently supported for index-organized tables:
CREATE TABLE with LOB/BFILE/VARRAY columns,
partitioning/PARALLEL/CREATE TABLE AS SELECT options,
ALTER TABLE with ADD/MODIFY column options, CREATE INDEX
*Action:   Do not use the disallowed feature(s) in this release.
6) Re-running the create table statement in step 5 without the MAPPING TABLE clause works fine. Not surprisingly an attempt to create a secondary local bitmap index on this table fails as there's no mapping table, like so...
CREATE BITMAP INDEX IOTObj_Table_BMI1 ON IOTObj_Table (numberData)
LOCAL STORAGE (INITIAL 1M PCTINCREASE 0 NEXT 512K) NOLOGGING PARALLEL;
CREATE TABLE with LOB/BFILE/VARRAY columns,
partitioning/PARALLEL/CREATE TABLE AS SELECT options,
ALTER TABLE with ADD/MODIFY column options, CREATE INDEX
*Action:   Do not use the disallowed feature(s) in this release.
CREATE BITMAP INDEX IOTObj_Table_BMI1 ON IOTObj_Table (numberData)
LOCAL STORAGE (INITIAL 1M PCTINCREASE 0 NEXT 512K) NOLOGGING PARALLEL
Error at Command Line:99 Column:13
Error report:
SQL Error: ORA-00903: invalid table name
00903. 00000 - "invalid table name"
7) Creating a secondary local b-tree index is fine, like so...
SQL> CREATE INDEX IOTObj_Table_I1 ON IOTObj_Table (numberData)
LOCAL STORAGE (INITIAL 1M PCTINCREASE 0 NEXT 512K) NOLOGGING PARALLEL;
index IOTOBJ_TABLE_I1 created.
8) A quick test to ensure object table ok...
SQL> INSERT INTO IOTObj_Table VALUES (IOT_Type('DEF456',500));
SQL> 1 rows inserted.
SQL> SELECT * FROM IOTObj_Table;
TEXTDATA NUMBERDATA
DEF456     500

Thanks Dan,
the intention is to range partition based on the initial character, so A* -> Text_Part_A, B* -> Text_Part_B, and so on.
Here's an example, using an empty IOTObj_Table as created previously.
1) Set up & confirm some test data (two 'D's, one 'N', and two 'Z's)
SQL> INSERT INTO IOTObj_Table VALUES (IOT_Type('DEF456',500));
SQL> INSERT INTO IOTObj_Table VALUES (IOT_Type('DDD111',510));
SQL> INSERT INTO IOTObj_Table VALUES (IOT_Type('N3000',515));
SQL> INSERT INTO IOTObj_Table VALUES (IOT_Type('ZZ1212',520));
SQL> INSERT INTO IOTObj_Table VALUES (IOT_Type('Z111X',530));
SQL> COMMIT;
SQL> SELECT * FROM IOTObj_Table;
TEXTDATA NUMBERDATA
DDD111     510
DEF456     500
N3000     515
Z111X     530
ZZ1212     520
2) Just to prove our IOT is enforcing the Primary Key based on the TextData attribute, try to insert a duplicate
SQL> INSERT INTO IOTObj_Table VALUES (IOT_Type('Z111X',530));
Error starting at line 141 in command:
INSERT INTO IOTObj_Table VALUES (IOT_Type('Z111X',530))
Error report:
SQL Error: ORA-00001: unique constraint (OCDataSystems.SYS_IOT_TOP_84235) violated
00001. 00000 - "unique constraint (%s.%s) violated"
*Cause:    An UPDATE or INSERT statement attempted to insert a duplicate key.
For Trusted Oracle configured in DBMS MAC mode, you may see
this message if a duplicate entry exists at a different level.
*Action:   Either remove the unique restriction or do not insert the key.
3) Now confirm that our data has been slotted into the range-based partition we expect using the PARTITION clause of SELECT...
- The two 'D's...
SQL> SELECT * FROM IOTObj_Table PARTITION (Text_Part_D);
TEXTDATA NUMBERDATA
DDD111     510
DEF456     500
- The single 'N'...
SQL> SELECT * FROM IOTObj_Table PARTITION (Text_Part_N);
TEXTDATA NUMBERDATA
N3000     515
- The two 'Z's...
SQL> SELECT * FROM IOTObj_Table PARTITION (Text_Part_Z);
TEXTDATA NUMBERDATA
Z111X     530
ZZ1212     520
4) And to wrap up confirm an empty partition
SELECT * FROM IOTObj_Table PARTITION (Text_Part_W);

Creation of bitmap index taking long time

Hi
I have OLTP compression enabled on the table
CREATE BITMAP INDEX
I1 ON
T1(
col 1Asc
NOLOGGING TABLESPACE ts_index01
taking very long time.
The wait event is : cell single block physical read.
Any ideas what I can do?
Thank u

Hi Marc
thanks for your answer. The issue is this is a cOTS product(Siebel Analytics). The indexes are created by DAC(Informatica) automatically. I do not have away to "create index index_name parallel degree 24" clause in there.
Thanks

How to save an icon as a bitmap file in illustrator with transparency?

Hello I need help,
I don't normally work with bitmap files however I find myself in need to save out a set of icons in this particular format for a client to use with their own software on a pc. this software can only import/use .bmp files.
In my export options .bmp is an option but I am unable to save it out with a transparent background which is a big issue. The result is an icon with white background and I need it to be transparent.
I tried pasting these icons to photoshop but I only is a portable bitmap format in the "save as" menu which I don't think will work as it creates a .PMP file and I don't think it will work with client's software. I am on a mac, with illustrator CC as well as photoshop.
I would very much appreciate help with this, I have been trying to figure this out for 2 hours now. Thank you in advance.

When I have created bitmap icons in the past (used to work for a software company) I used to create them with either a icon creator tool (Axialis) or directly in photoshop.
For color depths 24 BPP or less, the transparency is coded by using a fixed color. Each pixel that have this exact color will be converted as transparent when the image is loaded in the toolbar. Usually, the color used is green RGB(0,255,0) or magenta RGB(255,0,255). The problem of this method is that if you use a pixel of that color in your icon image (not the background), it will be converted as transparent. The other issue is the poor quality of the borders (around the icons) because it does not permit smooth transparency. In other words, a pixel is either 100% transparent or 100% opaque, there is no variable transparency. It results in "aliasing" on borders for icons with rounded shapes.
This is an old technique so you will struggle to get the desired results but worth you having a look for "creating bmp icons with transparency" online.

Effect of bitmap indices on inserts

Hi,
I have a table where the are 6 indices out of which 4 are bitmap. The table consist of a 110 million records.
-- When I am inserting records in my table how is the presence of the bitmap index going to affect the performance
of my insert statements.
-- Do I need to drop and recreate my indices? If yes do I need to drop all indices or only the bitmap ones.?
-- Also if during an insert the columns on which the index(particularly bitmap) is created is NOT referred then will it
still affect the perforamnce of the insert statements.?
Wolud appreciate your help.
Thanx...

That is not correct. The thing you lock is a single index entry - and there may be multiple index entries for the bitmap on "MARRIED". Your statement might be true for a fairly small table, but that's a coincidence and not design.Session 1
==========
DWDEVDB$SYS> create table test (id number, name varchar2(2));
Table created.
DWDEVDB$SYS> create bitmap index test_idx on test(id);
Index created.
DWDEVDB$SYS> insert into test values(1,'a');
1 row created.
DWDEVDB$SYS> insert into test values(1,'b');
1 row created.
DWDEVDB$SYS> insert into test values(1,'c');
1 row created.
DWDEVDB$SYS> insert into test values(1,'d');
1 row created.
DWDEVDB$SYS> insert into test values(2,'e');
1 row created.
DWDEVDB$SYS> insert into test values(2,'f');
1 row created.
DWDEVDB$SYS> insert into test values(2,'g');
1 row created.
DWDEVDB$SYS> insert into test values(2,'h');
1 row created.
DWDEVDB$SYS> commit;
Commit complete.
DWDEVDB$SYS> insert into test values(2,'i');
1 row created.
DWDEVDB$SYS> insert into test select * from test;
8 rows created.
DWDEVDB$SYS> insert into test select * from test;
16 rows created.
DWDEVDB$SYS> insert into test select * from test;
32 rows created.
DWDEVDB$SYS> insert into test select * from test;
64 rows created.
DWDEVDB$SYS> insert into test select * from test;
128 rows created.
DWDEVDB$SYS> insert into test select * from test;
256 rows created.
DWDEVDB$SYS> insert into test select * from test;
512 rows created.
DWDEVDB$SYS> insert into test select * from test;
1024 rows created.
DWDEVDB$SYS> insert into test select * from test;
2048 rows created.
DWDEVDB$SYS> insert into test select * from test;
4096 rows created.
DWDEVDB$SYS> insert into test select * from test;
8192 rows created.
DWDEVDB$SYS> insert into test select * from test;
16384 rows created.
DWDEVDB$SYS> insert into test select * from test;
32768 rows created.
DWDEVDB$SYS> insert into test select * from test;
65536 rows created.
DWDEVDB$SYS> insert into test select * from test;
131072 rows created.
DWDEVDB$SYS> commit;
Commit complete.
DWDEVDB$SYS> insert into test values(2,'Z');
1 row created.
----------------------Now go to session 2
DWDEVDB$SYS>Session 2
==========
DWDEVDB$SYS> update test set name='T' where name='e' and id=2;
1 row created.
32768 rows updated.
------------Update did not hang here even though it is updating a row with id=2 becuase rows being affected here might not be in the segment which is locked by the first session.
DWDEVDB$SYS> insert into test values(2,'y');
----------------It hangs here because now it is inserting values in a bitmap segment which is alreay locked by the first session because first session is also locking probably last bitmap segment and same segment is being tried to be locked by this sessionSalman

Bitmap indexes

hi everyone,
There is table t
and there are several bitmap one-column indexes
i1 on t(c1)
i2 on t(c2)
i3 on t(c3)
Column C1 is not nullable.
Columns C2 and C3 is nullable.
There is query
select /*+ index_combine(t) */
from t
where c1 = :1
   and c2 in (:2, 'X')
   and c3 = :3
| Id | Operation                     |
|   0 | SELECT STATEMENT              |
|   1 | TABLE ACCESS BY INDEX ROWID |
|   2 |   BITMAP CONVERSION TO ROWIDS |
|   3 |    BITMAP AND                 |
|   4 |     BITMAP INDEX SINGLE VALUE |
|   5 |     BITMAP INDEX SINGLE VALUE |
|   6 |     BITMAP OR                 |
|   7 |      BITMAP INDEX SINGLE VALUE|
|   8 |      BITMAP INDEX SINGLE VALUE|
---------------------------------------Fine.
But if I create following indexes (and drop previous)
create bitmap index idx1 on t(C1, C2);
create bitmap index idx2 on t(C1, C3);
then the plan of the query above is following:
| Id | Operation                    |
|   0 | SELECT STATEMENT             |
|   1 | TABLE ACCESS BY INDEX ROWID |
|   2 |   BITMAP CONVERSION TO ROWIDS|
|   3 |    BITMAP INDEX SINGLE VALUE |
--------------------------------------And the question:
why the plan does not consist BITMAP AND ?
Is it possible to scan both new indexes in the query with BITMAP AND?
Thanks

793769 wrote:
Jonathan Lewis wrote:
I think this means there's a hole in the optimizer's legal strategies that you might have to fill by other methods.Do I right understand that it is impossible to combine bitmap non-one-column indexes?No, you're generalising from the particular - thus are myths created.
I have demonstrated a case where two bitmap indexes start with the same column+, and the optimizer therefore refuses to do a "bitmap and" between these two indexes when you have where clause that uses equality on the common first column and equalities on the seperate second columns. This is a very small subset of query patterns involving combinations of "non-one-column" (multi-column) indexes.
For example - why don't you try recreating your (c1, c3) index as (c3, c1) to see what the optimizer can do ?
In my example it produced the following path:
| Id | Operation                    | Name    | Rows | Bytes | Cost |
|   0 | SELECT STATEMENT             |         |    10 | 1250 |     6 |
|   1 | TABLE ACCESS BY INDEX ROWID | T1      |    10 | 1250 |     6 |
|   2 |   BITMAP CONVERSION TO ROWIDS|         |       |       |       |
|   3 |    BITMAP AND                |         |       |       |       |
|* 4 |     BITMAP INDEX SINGLE VALUE| T1_B1B2 |       |       |       |
|   5 |     BITMAP MERGE             |         |       |       |       |
|* 6 |      BITMAP INDEX RANGE SCAN | T1_B3B1 |       |       |       |
Predicate Information (identified by operation id):
   4 - access("C1"=5 AND "C2"=50)
   6 - access("C3"=50)
       filter("C3"=50)So it is combining two multi column indexes - but it doesn't appear to be able to use the common column twice to make the second index access as efficient as possible. (This plan appeared for 10.2.0.3 and 11.2.0.2).
Regards
Jonathan Lewis

IGS create bitmap imagine

Similar Messages

Maybe you are looking for