Subpartition issue.

Hello Folks,
I am having 1 table, and it has 3 partitions and one of it's having max value and I want to create subpartition inside that partition. When I have created subpartition it's got created with system generated name. When I am trying to explicitly specify that name it's throwing me below error.
alter table x_event split partition LOG_MAX
AT(TO_DATE(' 2012-01-01 00:00:00','SYYYY-MM-DD HH24:MI:SS','NLS_CALENDAR=GREGORIAN'))
INTO (PARTITION Y11M12 SUBPARTITIONS Y11M12_FSM VALUES('0', '1', '2', '3', '4', '5', '6', '7', '8', '9')) UPDATE GLOBAL INDEXES ; 2 3
INTO (PARTITION Y11M12 SUBPARTITIONS Y11M12_FSM VALUES('0', '1', '2', '3', '4', '5', '6', '7', '8', '9')) UPDATE GLOBAL INDEXES
ERROR at line 3:
ORA-14156: invalid number of subpartitions specified in [SUBPARTITIONS |
SUBPARTITION TEMPLATE] clause
has anybody has got the same issue before ?

HG,
I tried using the code you posted here but it got lots of syntax errors and moreover it has subpatition by list and trying to use hash subpartitioning style. So based on your information, i created table with 3 range partitions a list partitions (see sql for more details).
Sql for creating range/list composite partitioned table
CREATE TABLE klondike.xlog_event (
xlog_even_id NUMBER (38) NOT NULL,
xlog_date DATE NOT NULL,
xlog_id NUMBER (38) NOT NULL,
xlog_event_type_id NUMBER (38) NOT NULL,
xlog_event_status_id NUMBER (38) NOT NULL,
detail_count NUMBER (38) NOT NULL,
start_date timestamp (6) NOT NULL,
end_date timestamp (6) NOT NULL
TABLESPACE xlog_event_data
LOGGING
PARTITION BY RANGE (xlog_date)
SUBPARTITION BY LIST (xlog_event_type_id)
*(PARTITION y09m12*
VALUES LESS THAN
*( (TO_DATE ('2010-01-01 00:00:00', 'YYYY-MM-DD HH24:MI:SS')))*
LOGGING
NOCOMPRESS
TABLESPACE xlog_event_data
*(SUBPARTITION sub_y09m12 VALUES (200) TABLESPACE xlog_event_data),*
PARTITION y10m12
VALUES LESS THAN
*( (TO_DATE ('2011-01-01 00:00:00', 'YYYY-MM-DD HH24:MI:SS')))*
LOGGING
NOCOMPRESS
TABLESPACE xlog_event_data
*(SUBPARTITION sub_y10m12 VALUES (300) TABLESPACE xlog_event_data),*
PARTITION xlog_max
VALUES LESS THAN (maxvalue)
LOGGING
NOCOMPRESS
TABLESPACE xlog_event_data
SUBPARTITION y06_fsm
VALUES (0, 1, 2, 3, 4, 5, 6, 7, 8, 9)
TABLESPACE xlog_event_data,
SUBPARTITION y06_fsd
VALUES (50, 51, 52, 53, 54, 55, 56, 57, 58, 59)
TABLESPACE xlog_event_data,
SUBPARTITION y06_mis
VALUES (40, 41, 42, 43, 44, 45, 46, 47, 48, 49)
TABLESPACE xlog_event_data,
SUBPARTITION y06_imp
VALUES (20, 21, 22, 23, 24, 25, 26, 27, 28, 29)
TABLESPACE xlog_event_data,
SUBPARTITION y06_omp
VALUES (30, 31, 32, 33, 34, 35, 36, 37, 38, 39)
TABLESPACE xlog_event_data,
SUBPARTITION y06_iep
VALUES (60, 61, 62, 63, 64, 65, 66, 67, 68, 69)
TABLESPACE xlog_event_data,
SUBPARTITION y06_oep
VALUES (70, 71, 72, 73, 74, 75, 76, 77, 78, 79)
TABLESPACE xlog_event_data,
SUBPARTITION y06_emd
VALUES (80, 81, 82, 83, 84, 85, 86, 87, 88, 89)
TABLESPACE xlog_event_data,
SUBPARTITION y06_man
VALUES (100, 101, 102, 103, 104, 105, 106, 107, 108, 109)
TABLESPACE xlog_event_data,
SUBPARTITION y06_evt
VALUES (110, 111, 112, 113, 114, 115, 116, 117, 118, 119)
TABLESPACE xlog_event_data,
SUBPARTITION y06_msa
VALUES (90, 91, 92, 93, 94, 95, 96, 97, 98, 99)
TABLESPACE xlog_event_data
Later I split LOG_MAX patition and split subpatition Y06_FSM into Y11M12_FSM , see below for synatx.
ALTER TABLE XLOG_EVENT
SPLIT SUBPARTITION Y06_FSM
VALUES (0,1,2,3,4)
INTO (SUBPARTITION Y11M12_FSM TABLESPACE XLOG_EVENT_DATA
*, SUBPARTITION Y06_FSM)*
UPDATE GLOBAL INDEXES;
ALTER TABLE xlog_event
SPLIT PARTITION xlog_max AT
*((TO_DATE('2012-01-01 00:00:00','YYYY-MM-DD HH24:MI:SS')))*
INTO (PARTITION y11m12
TABLESPACE xlog_event_data
*, PARTITION xlog_max);*
Once you are done later you can rename system generated subpartition name with your choice of name using following
E.g.
ALTER TABLE XLOG_EVENT RENAME SUBPARTITION SYS_SUBP143 TO Y11M12_1;
Let me know if this helps you out and answer your question.
Regards

Similar Messages

Issue while using SUBPARTITION clause in the MERGE statement in PLSQL Code

Hello All,
I am using the below code to update specific sub-partition data using oracle merge statements.
I am getting the sub-partition name and passing this as a string to the sub-partition clause.
The Merge statement is failing stating that the specified sub-partition does not exist. But the sub-partition do exists for the table.
We are using Oracle 11gr2 database.
Below is the code which I am using to populate the data.
declare
ln_min_batchkey PLS_INTEGER;
ln_max_batchkey PLS_INTEGER;
lv_partition_name VARCHAR2 (32767);
lv_subpartition_name VARCHAR2 (32767);
begin
FOR m1 IN ( SELECT (year_val + 1) AS year_val, year_val AS orig_year_val
FROM ( SELECT DISTINCT
TO_CHAR (batch_create_dt, 'YYYY') year_val
FROM stores_comm_mob_sub_temp
ORDER BY 1)
ORDER BY year_val)
LOOP
lv_partition_name :=
scmsa_handset_mobility_data_build.fn_get_partition_name (
p_table_name => 'STORES_COMM_MOB_SUB_INFO',
p_search_string => m1.year_val);
FOR m2
IN (SELECT DISTINCT
'M' || TO_CHAR (batch_create_dt, 'MM') AS month_val
FROM stores_comm_mob_sub_temp
WHERE TO_CHAR (batch_create_dt, 'YYYY') = m1.orig_year_val)
LOOP
lv_subpartition_name :=
scmsa_handset_mobility_data_build.fn_get_subpartition_name (
p_table_name => 'STORES_COMM_MOB_SUB_INFO',
p_partition_name => lv_partition_name,
p_search_string => m2.month_val);
                    DBMS_OUTPUT.PUT_LINE('The lv_subpartition_name => '||lv_subpartition_name||' and lv_partition_name=> '||lv_partition_name);
IF lv_subpartition_name IS NULL
THEN
                         DBMS_OUTPUT.PUT_LINE('INSIDE IF => '||m2.month_val);
INSERT INTO STORES_COMM_MOB_SUB_INFO T1 (
t1.ntlogin,
t1.first_name,
t1.last_name,
t1.job_title,
t1.store_id,
t1.batch_create_dt)
SELECT t2.ntlogin,
t2.first_name,
t2.last_name,
t2.job_title,
t2.store_id,
t2.batch_create_dt
FROM stores_comm_mob_sub_temp t2
WHERE TO_CHAR (batch_create_dt, 'YYYY') = m1.orig_year_val
AND 'M' || TO_CHAR (batch_create_dt, 'MM') =
m2.month_val;
ELSIF lv_subpartition_name IS NOT NULL
THEN
                    DBMS_OUTPUT.PUT_LINE('INSIDE ELSIF => '||m2.month_val);
MERGE INTO (SELECT *
FROM stores_comm_mob_sub_info
SUBPARTITION (lv_subpartition_name)) T1 --> Issue Here
USING (SELECT *
FROM stores_comm_mob_sub_temp
WHERE TO_CHAR (batch_create_dt, 'YYYY') =
m1.orig_year_val
AND 'M' || TO_CHAR (batch_create_dt, 'MM') =
m2.month_val) T2
ON (T1.store_id = T2.store_id
AND T1.ntlogin = T2.ntlogin)
WHEN MATCHED
THEN
UPDATE SET
t1.postpaid_totalqty =
(NVL (t1.postpaid_totalqty, 0)
+ NVL (t2.postpaid_totalqty, 0)),
t1.sales_transaction_dt =
GREATEST (
NVL (t1.sales_transaction_dt,
t2.sales_transaction_dt),
NVL (t2.sales_transaction_dt,
t1.sales_transaction_dt)),
t1.batch_create_dt =
GREATEST (
NVL (t1.batch_create_dt, t2.batch_create_dt),
NVL (t2.batch_create_dt, t1.batch_create_dt))
WHEN NOT MATCHED
THEN
INSERT (t1.ntlogin,
t1.first_name,
t1.last_name,
t1.job_title,
t1.store_id,
t1.batch_create_dt)
VALUES (t2.ntlogin,
t2.first_name,
t2.last_name,
t2.job_title,
t2.store_id,
t2.batch_create_dt);
END IF;
END LOOP;
END LOOP;
COMMIT;
end;
Much appreciate your inputs here.
Thanks,
MK.
(SORRY TO POST THE SAME QUESTION TWICE).
Edited by: Maddy on May 23, 2013 10:20 PM

Duplicate question

Where did the Partitions and SubPartitions go?

I created a table with partition Range (Transaction_Date, Retention_Period) and hash (Record_Id) subpartition template (for 32 subpartitions)
Then I add more partitions and while the loop is going on I can get counts of partitions and subpartitions. The job finished and my log table shows about 1800 partitions added and there should be 32 subpartitions for each of the partitions. However, user_tab_partitions shows zero records for the table, and user_tab_subpartitions also show zero record. After a few minutes the partitions show up but no subpartitions. The indexes on the table have also disappeared (one local and one global)
Any explanation for this behaviour?
Working on Exadata 11.2.0.3
Querying
USER_TABLES
USER_TAB_PARTITIONS
USER_TAB_SUBPARTITIONS
USER_INDEXES

>
Step 1. Create Table xyz (c1 date, c2 integer c3 integer, etc)
partition by range (c1,c2)
subpartition template (s01, s02... s32)
create index i1 on xyz (c1,c2,c3) local;
Then, since I want to create about 1800 partitions I have a procedure that has a "loop around" ALTER TABLE add Partition .. until all the partitions are created. This is the "Job" which while running I query USER_TAB_PARTITIONS and USER_TAB_SUBPARTITIONS to see how things are progressing. And Yes ALTER Table has no progressing to verify.
So al the partitions get created. No errors from the procedure to go through creating all the partitions. So I would expect that at the end I should get to see all the new partitions for the Table. Instead I get "no records" from USER_TAB_PARTITIONS and USER_TAB_SUBPARTITIONS.
I am also aware that "ALTER TABLE ADD PARTITION .." cannot make indexes go away. However, if the query on USER_INDEXES returns nothing, what happend to the Index created before the partitions were added?
I am not using DBMS_REDEFINITION. The only procedure is to add partitions one at a time for each date for 3 years. If you have a better way than a procedure please advise accordingly.
>
In order to help you the first step is to understand what problem you are dealing with. Then comes trying to determine what options are available for addressing the problem. There are too many times , and yours may, or may not, be another one, where people seem to have settled on a solution before they have really identified the problem.
Anytime someone mentions the use of dynamic SQL it raises a red flag. And when that use is for DDL, rather than DMl, it raises a REALLY BIG red flag.
Schema objects need to be managed properly and the DDL that creates them needs to be properly written and kept in some sort of version control.
Scripts and procedures that use dynamic SQL are more properly used to create DDL, not to execute it. That is, rather than use a procedure to dynamically create or alter a table you would use the procedure to dynamically create a DDL script that would create or alter the table.
Let's assume that you know for certain that your table really needs to have 1800 partitions, be subpartitioned the way you say and have partition and subpartitions names that you assign. Well, that would be a pain to hand-write 1800 partition definitions.
So you would create a procedure that would produce a CREATE TABLE script that had the proper clauses and syntax to specify those 1800 partitions. Your 'loop' would not EXECUTE an ALTER TABLE for each partition but would create the partition specification and modify the partition boundaries for each iteration through the loop. Sort of like
for i from 1 to 365 loop
add partition spec for startDate + i
end loop;The number of iterations would be a parameter and you would start with 2 or 3. Always test with the smallest code that will produce the correct results. If the code works for 3 days it will work for any larger reasonable number.
Then you would save that script in your version control system and run it to create the table. There would be nothing to monitor since there is just one script and when it is done it is done.
That would be a proper use of dynamic sql: to produce DDL, not to execute it.
Back to your issue. If I were your manager then based on what you posted I would expect you to already have
1. a requirements document that stated the problem (e.g. performance, data management) that was being addressed
2. test results that showed that your proposed solution (a table partitioned the way you posted) solves the problem
The requirements doc would have detail about what the performance/management issues are and what impact they are having
You also need to document what the possible solutions are, the relative merits of each solution and the factors you considered when ranking the solutions. That is, why is your particular partitioning scheme the best solution for the problem.
You should have test results that show the execution plans and performance you achieved by using a test version of your proposed table and indexes.
Until you have 'proven' that your solution will work as you expect I wouldn't recommend implementing the full-blown version of it.
1. Create a table MANUALLY that has 2 or three days worth of partitions.
2. Load those partitions with a representative amount of data
3. Execute test queries to query data from one of those partitions
4. Execute the same test queries against your current table
5. Capture the execution plans (the actual ones) for those queries. Verify that you are getting the performance improvements that you expected.
Once ALL of that prep work is done and you have concluded that your table/index design is correct then go back to work on writing a script/procedure that will produce (not execute) DDL to produce the main table and partitioning you designed.
Just an aside on what you posted. The indexes should be created AFTER the table and its partitions are created. If you are creating your local index first, as you post suggests, you are forcing Oracle to revamp it 1800 times when each partition is added. Just create the index after the table.
p.s. the number of posts anyone has is irrevelant. The only thing that matters is whether the advice or suggestions they provide is helpful. And the helpfullness of those is limited to, and based on, ONLY the information a poster provides. For exampe, your proposed partitioning scheme might be perfectly appropriate for your use case or it could be totally inappropriate. We have no way of knowing without knowing WHY you chose that scheme.
But I haven't seen one like that so it makes me suspicious that you really need to get that complicated.

Selecting records from DEFAULT range-list subpartition

Is it possible to select records which belong to DEFAULT subpartition of a certain partition of a RANGE-LIST partitioned table, using subpartition pruning? Our task assumes creating partitions and subpartitions in a table dynamically before running ETL. But sometimes due to complexity of the path subpartition key goes from staging data to materialized views in data warehouse, we cannot predict all subpartition key values upfront. We can create DEFAULT subpartition for every partition though, and have Oracle place records which don't match any subpartition condition into that subpartition.
But later we need to split DEFAULT subpartition so that all records will go into their dedicated subpartitions, and DEFAULT will be left empty - other layers of our application need all records to be stored in subpartition other than DEFAULT in order to be available. For that, we need to know which keys are stored in DEFAULT subpartition. And the question is - how can we effectively achieve that?
The obvious "brute force" approach is to issue a query like:
select distinct subpart_key from mytable partition (myrangepartition) where not subpart_key in (list of all subpartition key values for this partition)
but it does not use partition pruning - I have checked execution plan. While it is possible to use only DEFAULT partition, this query will iterate through all subpartitions, which is huge performance impact. How can we instruct Oracle to use only DEFAULT subpartition?

is the solution. I have overlooked this syntax - now my life is much easier.

Code Insight Issue - SQL Developer 1.1 (1.1.0.23 Build Main 23-64)

Dear SQL Developer Team,
I have a slight issue with the Code Insight.
I have created a package with three procedures
create or replace PACKAGE PACKAGE1 AS
procedure test1 (inpar varchar2);
procedure test2 (inpar varchar2);
procedure test3 (inpr varchar2);
END PACKAGE1;
When I try and reference the procedures in the package code insight only shows two procedures (see this link for the screenshot http://i12.tinypic.com/3zqbuiv.gif)
Any ideas ?
Chris

Sorry Chris, been tied up. looked at this
1. created a PTN table. This is the DDL export of that table. Range partition on date.
-- DBMS_METADATA was unable to use TABLE_EXPORT to generate sql. Now trying to use TABLE.
CREATE TABLE "HR"."TABLE1"
( "ID" NUMBER,
"HIREDATE" DATE
) PCTFREE 10 PCTUSED 40 INITRANS 1 MAXTRANS 255
STORAGE(
BUFFER_POOL DEFAULT)
TABLESPACE "USERS"
PARTITION BY RANGE ("HIREDATE")
SUBPARTITION BY LIST ("ID")
(PARTITION "P1" VALUES LESS THAN (TO_DATE(' 2006-12-31 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
PCTFREE 10 PCTUSED 40 INITRANS 1 MAXTRANS 255
STORAGE(
BUFFER_POOL DEFAULT)
TABLESPACE "USERS"
( SUBPARTITION "SYS_SUBP21" VALUES (DEFAULT)
TABLESPACE "USERS") ,
PARTITION "P2" VALUES LESS THAN (TO_DATE(' 2007-01-31 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
PCTFREE 10 PCTUSED 40 INITRANS 1 MAXTRANS 255
STORAGE(
BUFFER_POOL DEFAULT)
TABLESPACE "USERS"
( SUBPARTITION "SYS_SUBP22" VALUES (DEFAULT)
TABLESPACE "USERS") ) ;
2. Export from Resultset tables in query. As insert statements
REM INSERTING into TABLE1
Insert into TABLE1 ("ID","HIREDATE") values (1,to_date('12-DEC-06','DD-MON-RR'));
Insert into TABLE1 ("ID","HIREDATE") values (2,to_date('21-JAN-07','DD-MON-RR'));
I'm also getting the others working well too. I 'm running the latest version that we are about to release a patch on so it should be good when it comes out.

Using PARTITION FOR/SUBPARTITION FOR syntax to insert

We are trying to use PARTITION FOR syntax (or, better, SUBPARTITION FOR syntax) to insert into a subpartitioned table.
http://docs.oracle.com/cd/E11882_01/server.112/e26088/sql_elements009.htm#i165979
08:26:46 GM_CS_CDR@oradev02> select * from v$version;
BANNER
Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
PL/SQL Release 11.2.0.3.0 - Production
CORE    11.2.0.3.0      Production
TNS for Solaris: Version 11.2.0.3.0 - Production
NLSRTL Version 11.2.0.3.0 - Production
5 rows selected.This table is has interval partitions on DATA_ORIGIN_ID and list subpartitions on TABLE_NAME.
First, a basic insert without specifying partitions:
08:10:05 GM_CS_CDR@oradev02> insert into key_ids2 (
08:11:51   2 DATA_ORIGIN_ID         ,
08:11:51   3 TABLE_NAME             ,
08:11:51   4 DUR_UK                 ,
08:11:51   5 DUR_UK_ID              )
08:11:51   6 select
08:11:51   7 12         ,
08:11:51   8 TABLE_NAME             ,
08:11:51   9 DUR_UK                 ,
08:11:51 10 DUR_UK_ID
08:11:51 11 from key_ids where table_name = 'PART'
08:11:51 12 and rownum <= 10;
10 rows created.Verifying SUBPARTITION FOR syntax on a SELECT:
08:19:43 GM_CS_CDR@oradev02>
08:26:45 GM_CS_CDR@oradev02>
08:26:45 GM_CS_CDR@oradev02>
08:26:45 GM_CS_CDR@oradev02>
08:26:45 GM_CS_CDR@oradev02> select count(*) from key_ids2
08:26:45   2 subpartition for(12,'PART');
COUNT(*)
        10
1 row selected.But when we add a subpartition specification (to limit the lock to a single subpartition), we get a syntax error:
08:14:57 GM_CS_CDR@oradev02> insert into key_ids2 subpartition for(12,'PART') (
08:14:57   2 DATA_ORIGIN_ID         ,
08:14:57   3 TABLE_NAME             ,
08:14:57   4 DUR_UK                 ,
08:14:57   5 DUR_UK_ID              )
08:14:57   6 select
08:14:57   7 14         ,
08:14:57   8 TABLE_NAME             ,
08:14:57   9 DUR_UK||'!'                 ,
08:14:57 10 DUR_UK_ID
08:14:57 11 from key_ids
08:14:57 12 where table_name = 'PART'
08:14:57 13 and rownum <= 10;
insert into key_ids2 subpartition for(12,'PART') (
ERROR at line 1:
ORA-14173: illegal subpartition-extended table name syntaxSpecifying at the partition level did not work either:
08:14:58 GM_CS_CDR@oradev02> insert into key_ids2 partition for(14) (
08:15:23   2 DATA_ORIGIN_ID         ,
08:15:23   3 TABLE_NAME             ,
08:15:23   4 DUR_UK                 ,
08:15:23   5 DUR_UK_ID              )
08:15:23   6 select
08:15:23   7 14         ,
08:15:23   8 TABLE_NAME             ,
08:15:23   9 DUR_UK||'!'                 ,
08:15:23 10 DUR_UK_ID
08:15:23 11 from key_ids
08:15:23 12 where table_name = 'PART'
08:15:23 13 and rownum <= 10;
insert into key_ids2 partition for(14) (
ERROR at line 1:
ORA-14108: illegal partition-extended table name syntaxBut specifying explicit partition and subpartition does work:
08:17:45 GM_CS_CDR@oradev02> insert into key_ids2 partition (SYS_P15127) (
08:18:23   2 DATA_ORIGIN_ID         ,
08:18:23   3 TABLE_NAME             ,
08:18:23   4 DUR_UK                 ,
08:18:23   5 DUR_UK_ID              )
08:18:23   6 select
08:18:23   7 12         ,
08:18:23   8 TABLE_NAME             ,
08:18:23   9 DUR_UK||'!'                 ,
08:18:23 10 DUR_UK_ID
08:18:23 11 from key_ids
08:18:23 12 where table_name = 'PART'
08:18:23 13 and rownum <= 10;
10 rows created.
08:18:24 GM_CS_CDR@oradev02> insert into key_ids2 subpartition (SYS_SUBP15126) (
08:19:42   2 DATA_ORIGIN_ID         ,
08:19:42   3 TABLE_NAME             ,
08:19:42   4 DUR_UK                 ,
08:19:42   5 DUR_UK_ID              )
08:19:42   6 select
08:19:42   7 12         ,
08:19:42   8 TABLE_NAME             ,
08:19:42   9 DUR_UK||'!#'                 ,
08:19:42 10 DUR_UK_ID
08:19:42 11 from key_ids
08:19:42 12 where table_name = 'PART'
08:19:42 13 and rownum <= 10;
10 rows created.We have been successful in using the PARTITION FOR syntax for tables that were partitioned but not subpartitioned.
Any ideas?
Thanks,
Mike

I've created a simplified script to reproduce our issue. The use of the syntax on an INSERT INTO using VALUES still produces the same error.
Thanks,
Andy
select * from v$version;
create table part_test_tbl
data_origin_id NUMBER not null,
table_name VARCHAR2(30) not null,
dur_uk     VARCHAR2(250) not null,
dur_uk_id NUMBER
partition by range (data_origin_id) INTERVAL (1)
subpartition by list (TABLE_NAME)
SUBPARTITION TEMPLATE(
subpartition BLUE values ('BLUE'),
subpartition RED values ('RED'),
subpartition YELLOW values ('YELLOW'),
subpartition GREEN values ('GREEN'),
subpartition ORANGE values ('ORANGE')
(PARTITION DFLT_INTRVL VALUES LESS THAN (0)
subpartition BLUE values ('BLUE'),
subpartition RED values ('RED'),
subpartition YELLOW values ('YELLOW'),
subpartition GREEN values ('GREEN'),
subpartition ORANGE values ('ORANGE')
-- Create/Recreate indexes
create index PART_TEST_TBL_PK on PART_TEST_TBL (DATA_ORIGIN_ID, TABLE_NAME, DUR_UK, DUR_UK_ID)
compress 2 local;
create unique index PART_TEST_TBL_UK on PART_TEST_TBL (TABLE_NAME, DUR_UK_ID)
compress 1;
-- Create/Recreate primary, unique and foreign key constraints
alter table PART_TEST_TBL
add constraint PART_TEST_TBL_PK primary key (DATA_ORIGIN_ID, TABLE_NAME, DUR_UK) USING INDEX PART_TEST_TBL_PK;
alter table PART_TEST_TBL
add constraint PART_TEST_TBL_UK unique (TABLE_NAME, DUR_UK_ID) USING INDEX PART_TEST_TBL_UK;
--Add test data
BEGIN
   insert into PART_TEST_TBL (DATA_ORIGIN_ID, TABLE_NAME, DUR_UK, DUR_UK_ID)
   values (0, 'BLUE', '1', 1);
   insert into PART_TEST_TBL (DATA_ORIGIN_ID, TABLE_NAME, DUR_UK, DUR_UK_ID)
   values (0, 'BLUE', '2', 2);
   insert into PART_TEST_TBL (DATA_ORIGIN_ID, TABLE_NAME, DUR_UK, DUR_UK_ID)
   values (0, 'YELLOW', '3', 3);
   insert into PART_TEST_TBL (DATA_ORIGIN_ID, TABLE_NAME, DUR_UK, DUR_UK_ID)
   values (0, 'GREEN', '4', 4);
   insert into PART_TEST_TBL (DATA_ORIGIN_ID, TABLE_NAME, DUR_UK, DUR_UK_ID)
   values (0, 'ORANGE', '5', 5);
   insert into PART_TEST_TBL (DATA_ORIGIN_ID, TABLE_NAME, DUR_UK, DUR_UK_ID)
   values (1, 'BLUE', '6', 6);
   insert into PART_TEST_TBL (DATA_ORIGIN_ID, TABLE_NAME, DUR_UK, DUR_UK_ID)
   values (1, 'BLUE', '7', 7);
   insert into PART_TEST_TBL (DATA_ORIGIN_ID, TABLE_NAME, DUR_UK, DUR_UK_ID)
   values (1, 'YELLOW', '8', 8);
   insert into PART_TEST_TBL (DATA_ORIGIN_ID, TABLE_NAME, DUR_UK, DUR_UK_ID)
   values (1, 'GREEN', '9', 9);
   insert into PART_TEST_TBL (DATA_ORIGIN_ID, TABLE_NAME, DUR_UK, DUR_UK_ID)
   values (1, 'ORANGE', '10', 10);
   insert into PART_TEST_TBL (DATA_ORIGIN_ID, TABLE_NAME, DUR_UK, DUR_UK_ID)
   values (2, 'BLUE', '11', 11);
   insert into PART_TEST_TBL (DATA_ORIGIN_ID, TABLE_NAME, DUR_UK, DUR_UK_ID)
   values (2, 'BLUE', '12', 12);
   insert into PART_TEST_TBL (DATA_ORIGIN_ID, TABLE_NAME, DUR_UK, DUR_UK_ID)
   values (2, 'YELLOW', '13', 13);
   insert into PART_TEST_TBL (DATA_ORIGIN_ID, TABLE_NAME, DUR_UK, DUR_UK_ID)
   values (2, 'GREEN', '14', 14);
   insert into PART_TEST_TBL (DATA_ORIGIN_ID, TABLE_NAME, DUR_UK, DUR_UK_ID)
   values (2, 'ORANGE', '15', 15);
   insert into PART_TEST_TBL (DATA_ORIGIN_ID, TABLE_NAME, DUR_UK, DUR_UK_ID)
   values (10, 'BLUE', '16', 16);
   insert into PART_TEST_TBL (DATA_ORIGIN_ID, TABLE_NAME, DUR_UK, DUR_UK_ID)
   values (10, 'BLUE', '17', 17);
   insert into PART_TEST_TBL (DATA_ORIGIN_ID, TABLE_NAME, DUR_UK, DUR_UK_ID)
   values (10, 'YELLOW', '18', 18);
   insert into PART_TEST_TBL (DATA_ORIGIN_ID, TABLE_NAME, DUR_UK, DUR_UK_ID)
   values (10, 'GREEN', '19', 19);
   insert into PART_TEST_TBL (DATA_ORIGIN_ID, TABLE_NAME, DUR_UK, DUR_UK_ID)
   values (10, 'ORANGE', '20', 20);
   COMMIT;
END;
--Validate the subpartition_extended syntax
select count(*) from PART_TEST_TBL subpartition for(10,'BLUE');
--Show subpartition_extended syntax does not work on INSERT INTO
INSERT /*+APPEND */ INTO PART_TEST_TBL SUBPARTITION FOR (10,'BLUE')
(data_origin_id
,table_name
,dur_uk
,dur_uk_id)
VALUES
(10
,'BLUE'
,'16!'
,1016);
--Show subpartition_extended syntax does not work on INSERT INTO
INSERT /*+APPEND */ INTO PART_TEST_TBL SUBPARTITION FOR (10,'BLUE')
(data_origin_id
,table_name
,dur_uk
,dur_uk_id)
SELECT ptt.data_origin_id
      ,ptt.table_name
      ,ptt.dur_uk || '!' dur_uk
      ,ptt.dur_uk_id + 1000 dur_uk_id
FROM PART_TEST_TBL ptt
WHERE ptt.table_name = 'BLUE'
   AND ptt.data_origin_id = 10;
DROP TABLE part_test_tbl PURGE;-----
SQL> select * from v$version;
BANNER
Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
PL/SQL Release 11.2.0.3.0 - Production
CORE 11.2.0.3.0 Production
TNS for Solaris: Version 11.2.0.3.0 - Production
NLSRTL Version 11.2.0.3.0 - Production
SQL> create table part_test_tbl
2 (
3    data_origin_id NUMBER not null,
4    table_name VARCHAR2(30) not null,
5    dur_uk     VARCHAR2(250) not null,
6    dur_uk_id NUMBER
7 )
8 partition by range (data_origin_id) INTERVAL (1)
9 subpartition by list (TABLE_NAME)
10 SUBPARTITION TEMPLATE(
11    subpartition BLUE values ('BLUE'),
12    subpartition RED values ('RED'),
13    subpartition YELLOW values ('YELLOW'),
14    subpartition GREEN values ('GREEN'),
15    subpartition ORANGE values ('ORANGE')
16 )
17 (PARTITION DFLT_INTRVL VALUES LESS THAN (0)
18    (
19    subpartition BLUE values ('BLUE'),
20    subpartition RED values ('RED'),
21    subpartition YELLOW values ('YELLOW'),
22    subpartition GREEN values ('GREEN'),
23    subpartition ORANGE values ('ORANGE')
24    )
25 );
Table created
SQL> -- Create/Recreate indexes
SQL> create index PART_TEST_TBL_PK on PART_TEST_TBL (DATA_ORIGIN_ID, TABLE_NAME, DUR_UK, DUR_UK_ID)
2    compress 2 local;
Index created
SQL> create unique index PART_TEST_TBL_UK on PART_TEST_TBL (TABLE_NAME, DUR_UK_ID)
2    compress 1;
Index created
SQL> -- Create/Recreate primary, unique and foreign key constraints
SQL> alter table PART_TEST_TBL
2    add constraint PART_TEST_TBL_PK primary key (DATA_ORIGIN_ID, TABLE_NAME, DUR_UK) USING INDEX PART_TEST_TBL_PK;
Table altered
SQL> alter table PART_TEST_TBL
2    add constraint PART_TEST_TBL_UK unique (TABLE_NAME, DUR_UK_ID) USING INDEX PART_TEST_TBL_UK;
Table altered
SQL> --Add test data
SQL> BEGIN
2
3     insert into PART_TEST_TBL (DATA_ORIGIN_ID, TABLE_NAME, DUR_UK, DUR_UK_ID)
4     values (0, 'BLUE', '1', 1);
5
6     insert into PART_TEST_TBL (DATA_ORIGIN_ID, TABLE_NAME, DUR_UK, DUR_UK_ID)
7     values (0, 'BLUE', '2', 2);
8
9     insert into PART_TEST_TBL (DATA_ORIGIN_ID, TABLE_NAME, DUR_UK, DUR_UK_ID)
10     values (0, 'YELLOW', '3', 3);
11
12     insert into PART_TEST_TBL (DATA_ORIGIN_ID, TABLE_NAME, DUR_UK, DUR_UK_ID)
13     values (0, 'GREEN', '4', 4);
14
15     insert into PART_TEST_TBL (DATA_ORIGIN_ID, TABLE_NAME, DUR_UK, DUR_UK_ID)
16     values (0, 'ORANGE', '5', 5);
17
18     insert into PART_TEST_TBL (DATA_ORIGIN_ID, TABLE_NAME, DUR_UK, DUR_UK_ID)
19     values (1, 'BLUE', '6', 6);
20
21     insert into PART_TEST_TBL (DATA_ORIGIN_ID, TABLE_NAME, DUR_UK, DUR_UK_ID)
22     values (1, 'BLUE', '7', 7);
23
24     insert into PART_TEST_TBL (DATA_ORIGIN_ID, TABLE_NAME, DUR_UK, DUR_UK_ID)
25     values (1, 'YELLOW', '8', 8);
26
27     insert into PART_TEST_TBL (DATA_ORIGIN_ID, TABLE_NAME, DUR_UK, DUR_UK_ID)
28     values (1, 'GREEN', '9', 9);
29
30     insert into PART_TEST_TBL (DATA_ORIGIN_ID, TABLE_NAME, DUR_UK, DUR_UK_ID)
31     values (1, 'ORANGE', '10', 10);
32
33     insert into PART_TEST_TBL (DATA_ORIGIN_ID, TABLE_NAME, DUR_UK, DUR_UK_ID)
34     values (2, 'BLUE', '11', 11);
35
36     insert into PART_TEST_TBL (DATA_ORIGIN_ID, TABLE_NAME, DUR_UK, DUR_UK_ID)
37     values (2, 'BLUE', '12', 12);
38
39     insert into PART_TEST_TBL (DATA_ORIGIN_ID, TABLE_NAME, DUR_UK, DUR_UK_ID)
40     values (2, 'YELLOW', '13', 13);
41
42     insert into PART_TEST_TBL (DATA_ORIGIN_ID, TABLE_NAME, DUR_UK, DUR_UK_ID)
43     values (2, 'GREEN', '14', 14);
44
45     insert into PART_TEST_TBL (DATA_ORIGIN_ID, TABLE_NAME, DUR_UK, DUR_UK_ID)
46     values (2, 'ORANGE', '15', 15);
47
48     insert into PART_TEST_TBL (DATA_ORIGIN_ID, TABLE_NAME, DUR_UK, DUR_UK_ID)
49     values (10, 'BLUE', '16', 16);
50
51     insert into PART_TEST_TBL (DATA_ORIGIN_ID, TABLE_NAME, DUR_UK, DUR_UK_ID)
52     values (10, 'BLUE', '17', 17);
53
54     insert into PART_TEST_TBL (DATA_ORIGIN_ID, TABLE_NAME, DUR_UK, DUR_UK_ID)
55     values (10, 'YELLOW', '18', 18);
56
57     insert into PART_TEST_TBL (DATA_ORIGIN_ID, TABLE_NAME, DUR_UK, DUR_UK_ID)
58     values (10, 'GREEN', '19', 19);
59
60     insert into PART_TEST_TBL (DATA_ORIGIN_ID, TABLE_NAME, DUR_UK, DUR_UK_ID)
61     values (10, 'ORANGE', '20', 20);
62
63     COMMIT;
64 END;
65 /
PL/SQL procedure successfully completed
SQL> --Validate the subpartition_extended syntax
SQL> select count(*) from PART_TEST_TBL subpartition for(10,'BLUE');
COUNT(*)
         2
SQL> --Show subpartition_extended syntax does not work on INSERT INTO
SQL> INSERT /*+APPEND */ INTO PART_TEST_TBL SUBPARTITION FOR (10,'BLUE')
2 (data_origin_id
3 ,table_name
4 ,dur_uk
5 ,dur_uk_id)
6 VALUES
7 (10
8 ,'BLUE'
9 ,'16!'
10 ,1016);
INSERT /*+APPEND */ INTO PART_TEST_TBL SUBPARTITION FOR (10,'BLUE')
(data_origin_id
,table_name
,dur_uk
,dur_uk_id)
VALUES
(10
,'BLUE'
,'16!'
,1016)
ORA-14173: illegal subpartition-extended table name syntax
SQL> --Show subpartition_extended syntax does not work on INSERT INTO
SQL> INSERT /*+APPEND */ INTO PART_TEST_TBL SUBPARTITION FOR (10,'BLUE')
2 (data_origin_id
3 ,table_name
4 ,dur_uk
5 ,dur_uk_id)
6 SELECT ptt.data_origin_id
7        ,ptt.table_name
8        ,ptt.dur_uk || '!' dur_uk
9        ,ptt.dur_uk_id + 1000 dur_uk_id
10    FROM PART_TEST_TBL ptt
11   WHERE ptt.table_name = 'BLUE'
12     AND ptt.data_origin_id = 10;
INSERT /*+APPEND */ INTO PART_TEST_TBL SUBPARTITION FOR (10,'BLUE')
(data_origin_id
,table_name
,dur_uk
,dur_uk_id)
SELECT ptt.data_origin_id
      ,ptt.table_name
      ,ptt.dur_uk || '!' dur_uk
      ,ptt.dur_uk_id + 1000 dur_uk_id
FROM PART_TEST_TBL ptt
WHERE ptt.table_name = 'BLUE'
   AND ptt.data_origin_id = 10
ORA-14173: illegal subpartition-extended table name syntax
SQL> DROP TABLE part_test_tbl PURGE;
Table dropped
SQL>

Subpartition Template COMPRESS NOCOMPRESS parameter

Hi ,
I'm trying to create a table with subpartitions by list already partitioned by list,
I want to configure that some of my subpartitions are compressed and the rest nocompressed,
but I couldn't find how to specify it,
I could specify if the partition at all is compressed or not but not a subpartition level,
Thanks in advance

Hi,
I'm afraid it's not possible to specify this at the subpartition level at the moment.
I have logged an enhancement request on this.
Thanks for reporting this issue,
David

New DVR Issues (First Run, Channel Switching, etc.)

I've spent the last 30 minutes trying to find answers through the search with no luck, so sorry if I missed something.
I recently switched to FIOS from RCN cable in New York. I've gone through trying to setup my DVR and am running into issues and was hoping for some answers.
1. I setup two programs to record at 8PM, I was watching another channel at the time and only half paying attention. Around 8:02 I noticed a message had popped up asking if I would like to switch channels to start recording. I was expecting it to force it to switch like my old DVR, but in this case it didn't switch and I missed the first two minutes of one of the shows. I typically leave my DVR on all day and just turn off the TV, this dual show handling will cause issues with that if I forget to turn off the DVR. Is there a setting I can change that will force the DVR to choose one of the recording channels?
2. I setup all my recordings for "First Run" because I only want to see the new episodes. One show I setup was The Daily Show on comedy central, which is shown weeknights at 11pm and repeated 3-4 times throughout the day. My scheduled recordings is showing all these as planned recordings even though only the 11pm show is really "new". Most of the shows I've setup are once a week so they aren't a problem, but this seems like it will quickly fill my DVR. Any fixes?
Thanks for the help.
Solved!
Go to Solution.

I came from RCN about a year ago. Fios is different in several ways, not all of them desirable. Here are several ways to get--and fix--unwanted recordings from a series recording setup.
Some general principles.
Saving changes. When you originally create a series with options, or if you go back to edit the options for an existing series, You MUST save the Series Options changes. Pretty much everywhere else in the user interface, when you change an option, the change takes effect immediately--but not in Series Options. Look at the Series Options window. Look at the far right side. There is a vertical "Save" bar, which you must navigate to and click OK on to actually save your changes. Exiting the Series Options window without having first saved your changes loses all your attempted changes--immediately.
Default Series Options. This is accessed from [Menu]--DVR--Settings--Default Series Options. This will bring up the series options that will automatically be applied to the creation of a NEW series. The options for every previously created series will not be affected by a subsequent modification of the Default Series Options. You should set these options to the way you would like them to be for the majority of series recordings that you are likely to create. Be sure to SAVE your changes. This is what you will get when you select "Create Series Recording" from the Guide. When creating a new series recording where you think that you may want options different from the default, select "Create Series with Options" instead. Series Options can always be changed for any individual series set up later--but not for all series at once.
Non-series recordings. With Fios you have no directly available options for these. With RCN and most other DVRs, you can change the start and end times for individual episodes, including individual episodes that are also in a series. With Fios, your workarounds are to create a series with options for a single program, then delete the series later; change the series options if the program is already in a series, then undo the changes you made to the series options later; or schedule recordings of the preceding and/or following shows as needed.
And now, to the unwanted repeats.
First, make sure your series options for the specific series in question--and not just the series default options--include "First Run Only". If not, fix that and SAVE. Then check you results by viewing the current options using the Series Manager app under the DVR menu.
Second, and most annoying, the Guide can have repeat programs on your channel tagged as "New". It happens. Set the series option "Air Time" to "Selected Time". To make this work correctly, you must have set up the original series recording after selecting the program in the Guide at the exact time of a first run showing (11pm, in your case), and not on a repeat entry in the Guide. Then, even it The Daily Show is tagged as New for repeat showings, these will be ignored.
Third, another channel may air reruns of the program in your series recording, and the first showing of a rerun episode on the other channel may be tagged as "New". These can be ignored in your series if you set the series option "Channel" to "Selected Channel". Related to this, if there is both an SD and HD channel broadcasting you series program, you will record them both if the series option "Duplicates" is set to "Yes". However, when the Channel option is set to "Selected Channel", the Duplicates Option is always effectively "No", regardless of what shows up on the options screen.
As for you missing two minutes, I have sereral instances in which two programs start recording at the same time. To the best of my recollection, whenever the warning message has appeared, ignoring it has not caused a loss of recording time. You might have an older software version. Newest is v.1.8. Look at Menu--Settings--System Info. Or, I might not have noticed the loss of minutes. I regularly see up to a minute of previous programming at the start of a recording, or a few missing seconds at the beginning or end of a recording. There are a lot of possibilities for that, but the DVR clock being incorrect is not one of them. With RCN, the DVR clocks occasionally drifted off by as much as a minute and a half.

Pension issue Mid Month Leaving

Dear All,
As per rule sustem should deduct mid month joining/leaving/absences or transfer scenarios, the Pension/PF Basis will be correspondingly prorated. But our system is not doing this. In RT table i have found 3FC Pension Basis for Er c 01/2010                    0.00           6,500.00.
Employee leaving date is 14.04.2010. system is picking pension amout as 541. Last year it was coming right.
Please suggest.
Ashwani

Dear Jayanti,
We required prorata basis pension in case of left employees and system is not doing this. This is the issue. As per our PF experts Pension amount should come on prorata basis for left employees in case they left mid of month.System is doing prorata basis last year but from this year it is deducting 541. I am giving two RT cases of different years.
RT table for year 2010. DOL 26.04.2010
/111 EPF Basis              01/2010                    0.00           8,750.00
/139 VPF Basis              01/2010                    0.00           8,750.00
/3F1 Ee PF contribution     01/2010                    0.00           1,050.00
/3F3 Er PF contribution     01/2010                    0.00             509.00
/3F5 Ee Mon PF contribution 01/2010                    0.00           1,050.00
/3F6 Ee Ann PF contribution 01/2010                    0.00          12,600.00
/3F9 PF adm chrgs * 1,00,00 01/2010                    0.00              96.25
/3FA PF basis for Ee contri 01/2010                    0.00           8,750.00
/3FB PF Basis for Er Contri 01/2010                    0.00           8,750.00
/3FJ VPF basis for Ee contr 01/2010                    0.00           8,750.00
/3FL PF Basis for Er Contri 01/2010                    0.00           6,500.00
/3F4 Er Pension contributio 01/2010                    0.00             541.00
/3FC Pension Basis for Er c 01/2010                    0.00           6,500.00
/3FB PF Basis for Er Contri 01/2010                    0.00           8,750.00
/3FC Pension Basis for Er c 01/2010                    0.00           6,500.00
/3FJ VPF basis for Ee contr 01/2010                    0.00           8,750.00
/3FL PF Basis for Er Contri 01/2010                    0.00           6,500.00
/3R3 Metro HRA Basis Amount 01/2010                    0.00           8,750.00
1BAS Basic Salary           01/2010                    0.00           8,750.00
RT table for year 2009. DOL 27.10.2009
                                                                                /111 EPF Basis              07/2009                    0.00           9,016.13
/139 VPF Basis              07/2009                    0.00           9,016.13
/3F1 Ee PF contribution     07/2009                    0.00           1,082.00
/3F3 Er PF contribution     07/2009                    0.00             628.00
/3F5 Ee Mon PF contribution 07/2009                    0.00           1,082.00
/3F6 Ee Ann PF contribution 07/2009                    0.00           8,822.00
/3F9 PF adm chrgs * 1,00,00 07/2009                    0.00              99.18
/3FA PF basis for Ee contri 07/2009                    0.00           9,016.00
/3FB PF Basis for Er Contri 07/2009                    0.00           9,016.00
/3FJ VPF basis for Ee contr 07/2009                    0.00           9,016.00
/3FL PF Basis for Er Contri 07/2009                    0.00           5,452.00
/3FB PF Basis for Er Contri 07/2009                    0.00           9,016.00
/3FC Pension Basis for Er c 07/2009                    0.00           5,452.00
/3FJ VPF basis for Ee contr 07/2009                    0.00           9,016.00
/3FL PF Basis for Er Contri 07/2009                    0.00           5,452.00
/3R4 Non-metro HRA Basis Am 07/2009                    0.00           9,016.13
1BAS Basic Salary           07/2009                    0.00           9,016.13
Now please suggest what to do. where is the problem ? If have also checked EXIT_HINCALC0_002 but nothing written in it.
With Regards
Ashwani

Open PO Analysis - BW report issue

Hello Friends
I constructed a query in BW in order to show Open Purchase Orders. We have custom DSO populated with standard
datasource 2lis_02_itm (Purcahse Order Item). In this DSO we mapped the field ELIKZ to the infoobject 0COMP_DEL
(Delivery completed).
We loaded the data from ECC system for all POs and found the following issue for Stock Transport Purchase orders (DocType = UB).
We have a PO with 4 line items. For line items 10 and 20, Goods issued, Goods received and both the flags "Delivery
complete" and "Final delivery" checked. For line items 30 and 40, only delivery indicator note is issued for zero
quantity and Delivery complete flag is checked (Final delivery flag is not checked) in ECC system. For this PO, the
delivery completion indicator is not properly updated in the DSO for line items 30 and 40. The data looks like the
following:
DOC_NUM     DOC_ITEM      DOCTYPE     COMP_DEL
650000001       10     UB        X
650000001       20     UB        X
650000001       30     UB
650000001       40     UB
When we run the Open PO analysis report on BW side this PO is appearing in the report but the same is closed in ECC
system.
Any help is appreciated in this regard.
Thanks and Regards
sampath

Hi Priya and Reddy
   Thanks for your response.
                     Yes the indicator is checked in EKPO table for items 30 and 40 and delta is running regularly for more than 1 year and no issues with other POs. This is happening only for few POs of type Stock Transport (UB).
                    I already checked the changes in ME23N and the Delivery completed indicator was changed and it reflected in EKPO table. Further, i checked the PSA records for this PO and i am getting the records with the Delivery completed flag but when i update from PSA to DSO the delivery completed indicator is not updating properly.
                   In PSA, for item 30 i have the following entries. Record number 42 is capturing the value X for ELIKZ but after that i am getting two more records 43 and 44 with process key 10 and without X for ELIKZ. I think this is causing the problem.
Record No.    Doc.No.                    Item              Processkey         Rocancel     Elikz
    41               6500000001            30                    11                            X           ---
    42               6500000001            30                    11                            ---           X
    43               6500000001            30                    10                            X           ---
    44               6500000001            30                    10                            ---         ---
(Here --- means blank)
Thanks and Regards
sampath

HP LaserJet Enterprise 600 M602 driver issue

Hello,
I've got issue with 600-series printers. We use the latest UPD drivrer ver. 61.175.1.18849 and print from XenApp 6.5. The error occurs every time when users try to print jpg files from XenApp session. It only happens with 600 series printers and UPD.
Also I've tried to assign native 600-series driver ver. 6.3.9600.16384 and it works good. But with that driver system says that it's color printer and it brokes our printing reports. These reports are very important for us. So we can't use printer and that driver as well.
Printer installed on Windows Server 2012 R2. All clients are Windows 7 x64. XenApp Servers are Server 2008R2.
Is it possible to get fixed UPD driver or correct native driver for Server 2012 R2?
Regards,
Anatoly

I am sorry, but to get your issue more exposure I would suggest posting it in the commercial forums since this is a commercial printer. You can do this at Printers - LaserJet.
Click on New Post.
I hope this helps.
Please click “Accept as Solution ” if you feel my post solved your issue, it will help others find the solution.
Click the “Kudos Thumbs Up" on the right to say “Thanks” for helping!
Gemini02
I work on behalf of HP

Windows 7 displays error message when exiting +cursor issue

Two issues here. CS5 Phoshop on Wind 7 64 bit.
Physical processor count: 8
Processor speed: 3073 MHz
Built-in memory: 12279 MB
Free memory: 9577 MB
Memory available to Photoshop: 10934 MB
Memory used by Photoshop: 80 %
Image tile size: 128K
First issue is since the latest automatic Adobe update (why fix what isn't broken?) Every time I now exit Photoshop I get the message "Adobe QT Server has stoped working" and occasionally it happens when I exit bridge. Indesign is also behaving badly. I can no longer start a previous document from file manager without ID crashing out.
The other is the cursors in Clone and erase lose their edge (become invisable) for no reason - well not quite. Noise Ninja crashed Photoshop when I tried to use it. I reinstalled it and all is well. The cursor issue seems to be intermittant but came back (for no reason) after I reinstalled NN. I can't seem to change the cursor, no matter what I do. The problem is now seriously affecting how I work. Almost enough to go back to Win XP which ran CS5 Photoshop flawlessly.
Any help will be gratefully accepted.
Doug

function(){return A.apply(null,[this].concat($A(arguments)))}
doug87510 wrote:
The recent problem is the entire outline of the cursor (including the crosshair in the middle) was missing at any size of cursor. All I had was exactly what I'd get if I used a real spraygun.
Well, that issue is simply a matter of hitting the Caps Lock key. When Caps Lock is on, you'll see the cursor outline, and when it is off you'll see a crosshair. That's a feature, not a bug.
Glad to hear the 11.1 drivers are out. I will download them and try them now myself.
Regarding "Adobe QT" crashing... QT brings to mind QuickTime, though that is Apple, not Adobe. Do you have Apple QuickTime installed?
Regarding memory usage, with 12 GB of installed RAM, you should be able to set Photoshop to use 90% or more in Edit - Preferences - Performance.
-Noel

Issue in Creation of Periodicals for Contracts in CRM7.0

Hello,
I have a requirement to create Contracts in CRM7.0 system.
And I am doing this using the BAPI *BAPI_BUSPROCESSND_CREATEMULTI*
Good part is Contract Order gets created, but onlywith Header Details.
The issues i am facing --
1. I need to know what kind/type of data must be passed to the interface parameters, the F1 Help/Documentation is vague.
2. I am passing data in the INPUT FIELDS structure with the Object ID, Handle Number, Reference GUID and Fieldname,
here what does 'Logical Key' field indicate? What should be passed here.
What does 'REFERENCE KIND' field indicate, i have been passng 'A' for everything (to be frank i dont know whats its significance is!!).
3. With so much, My Order gets created but with less than half details, i.e. the Objects not getting created are - Partner, Product, terms/appointments, Status, LongTexts......
Any help/inputs would be appreciated.
Hope my problem is stated clearly ...
--Regards
Dedeepya

Hi Anu,
i found my solution by debugging with existing data or while creating it in CRMD_ORDER.
Ensure that you are passing a correct entry in INPUT_FIELDS structure.
As i haven't worked on rebates i woudlnt be able to help you, I suggest you debug to arrive at a solution.
You can preset your break-points at :-
1. FM - CRM_ORDER_MAINTAIN
2. CRM_ORDER_MAINTAIN_MULTI_OW -- Debug through the complete FM.
3. CRM_ORDER_PREPARE_MULTI_OW -- The data is set in this function module.
Regards
Dedeepya C

Issue in creation of plant related data at receiving server using BD10

Hi all,
This is regarding Material master creation using B10.I am using MATMAS05 message type for sending data from one system to another.Data is sent and received successfully.When i go in mm03 i can see all the views created successfully accept views related to PLANT.Please guide to resolve the issue.
When i entered into Log-
1)"The field MBEW-BKLAS is defined as a required field; it does not contain an entry".
2)"No material master data exists for material AB_08.04.09(30) in plant 4001".
My segemnt is as follows-
ZMATMAS05                      matmas05
       E1MARAM                        Master material general data (MARA)
           Z1KLART                        KLART----
My extention
           E1MARA1                        Additional Fields for E1MARAM
           E1MAKTM                        Master material short texts (MAKT)
           E1MARCM                        Master material C segment (MARC)
               Z1AUSPM                        E1AUSPMDistribution of Classification:----
My extention
               E1MARC1                        Additional Fields for E1MARCM
               E1MARDM                        Master material warehouse/batch segment (MARD)
               E1MFHMM                        Master material production resource/tool (MFHM)
               E1MPGDM                        Master material product group
               E1MPOPM                        Master material forecast parameter
               E1MPRWM                        Master material forecast value
               E1MVEGM                        Master material total consumption
               E1MVEUM                        Master material unplanned consumption
               E1MKALM                        Master material production version
           E1MARMM                        Master material units of measure (MARM)
           E1MBEWM                        Master material material valuation (MBEW)
           E1MLGNM                        Master material material data per warehouse number (MLGN)
           E1MVKEM                        Master material sales data (MVKE)
           E1MLANM                        Master material tax classification (MLAN)
           E1MTXHM                        Master material long text header
           E1CUCFG                        CU: Configuration data
       E1UPSLINK                      Reference from Object to Superior UPS
Thanks.
Edited by: sanu debu on Apr 27, 2009 7:10 PM

CREATE CONTROLFILE SET DATABASE "NEWDB" NORESETLOGS ARCHIVELOGAlso when you are setting a new database, the option should be RESETLOGS and not NORESETLOGS.
'D:\APP\ADMINISTRATOR\ORADATA\NEWDB\ONLINELOG\O1_MF_2_7FK0XKB8_.LOG
D:\APP\ADMINISTRATOR\ORADATA\NEWDB\DATAFILE\O1_MF_SYSTEM_7FK0SKN0_.DBFWhy underscore(_) at the end of the datafile name. Any specific reason ?

Issue in Creation of new Value Field in CO-PA

Hi,
I have a query in CO-PA Value Field Linking.
In my Development Client,
1. Created a New Value Field (No Transport Request Generated)
2. Linked to the above to new Conditon type created in SD. (Tranport request was generated) i.e. in Flow of Actual Values->Transfer of Billing Documents->Assign Value Fields
However then i try creating a new Value Field in my Production Client it throws a message 'You have no authorization to change Fields".
Is this an issue with authorization or i need to transport the Value field too from Development to Production client.
Please Advise.
Thanks in Advance,
Safi

Thanks Phaneendra for the response.
The creation of Value field did not create any tranportation request. Will this too be transported if i transport the Operating Concern.
Please Advise.
Thanks,
Safi

Subpartition issue.

Similar Messages

Maybe you are looking for