Create table Physical attributes clause

Guys,
In my current project, I need to create the table (unfortunately, we recently lost the main DBA). I have been supplied a standard create table clause this people are using for transaction table :
CREATE TABLE testtable
CITY VARCHAR2(50),
STATE VARCHAR2(2),
ZIPCODE VARCHAR2(9),
TABLESPACE space_DATA
PCTUSED 0
PCTFREE 10
INITRANS 1
MAXTRANS 255
STORAGE (
INITIAL 1M
NEXT 1M
MINEXTENTS 1
MAXEXTENTS 2147483645
PCTINCREASE 0
BUFFER_POOL DEFAULT
* I also need to create many Lookup kind of a table and need your help to find suggested values for: PCTUSED, pctfree, initrans, maxtrans, storage (initial, next, minextends, maxextends, pctincrease, buffer_pool) *
Please let me know if I need to use the different values for the above suggested attributes for lookup table vs transaction table?
Thank you soo much
-Raj

Hello,
It depends on your Tablespace.
If you use Dictionary Managed Tablespace (DMT), then you can use all these parameters.
If you use Locally Managed Tablespace (LMT) without Automatic Segment Space Management (ASSM) then you
may use the following parameters:
PCTUSED 0
PCTFREE 10
INITRANS 1
MAXTRANS 255
STORAGE ( BUFFER_POOL DEFAULT )
NB: PCTUSED = 0 is a very strange setting.
If you use LMT with ASSM then you don't have to use the PCTUSED parameter (you still may use PCTFREE).
About the BUFFER_POOL DEFAULT if you have just one Buffer it's not necessary the DEFAULT is always
the default value.
The BUFFER_POOL is useful when you have several Buffers (RECYCLE, KEEP and DEFAULT).
Hope this help.
Best regards,
Edited by: Lubiez Jean-Valentin on Jan 28, 2010 8:29 PM

Similar Messages

Create table with logging clause....

hi,
just reading this http://docs.oracle.com/cd/B19306_01/server.102/b14231/tables.htm#ADMIN01507
it mention under Consider Using NOLOGGING When Creating Tables:
The NOLOGGING clause also specifies that subsequent direct loads using SQL*Loader and direct load INSERT operations are not logged. S*ubsequent DML statements (UPDATE, DELETE, and conventional path insert) are unaffected by the NOLOGGING attribute of the table and generate redo.*
Help me with my understanding. Does it mean that when you create a table using logging clause and then when you need to do a direct loads, you can specify nologging to reduce the redo log. The nologging part will only work for this activity but not on DML operation even when you specify nologging?

sybrand_b wrote:
Nologging basically applies to the INSERT statement with the APPEND hint. Direct load means using this hint.
All other statements are always logging regardless of any table setting.>
Sybrand Bakker
Senior Oracle DBAi did a few test :
create table test
(id number) nologging;
Table created.
insert into test values (1);
1 row created.
commit;
Commit complete.
delete from test;
1 row deleted.
rollback;
Rollback complete.
select * from test;
ID
1there is no logging on table- level and tablespace - level. So what i am doing is to check -> Subsequent DML statements (UPDATE, DELETE, and conventional path insert) are unaffected by the NOLOGGING attribute of the table and generate redo."
the above makes me confuse cos isn't rollback related to UNDO tablespace not redo log. So one can still rollback even when it is in no logging.
REDO log is for rolling forward , recovery when there is a system crash... ..

[SOLVED] Create table and storage clause

Hi, I create a table whit lob ad so, I set some LOB storage clause:
CREATE TABLE W2_T_MESSAGE_NWSL (
KEY NUMBER,
T_MESSAGE CLOB DEFAULT EMPTY_CLOB(),
T_TEXTMESSAGE CLOB DEFAULT EMPTY_CLOB(),
T_FOOTER CLOB DEFAULT EMPTY_CLOB())
LOB (T_MESSAGE)
STORE AS (TABLESPACE LOBDATA CACHE READS RETENTION ENABLE STORAGE IN ROW),
LOB (T_TEXTMESSAGE)
STORE AS (TABLESPACE LOBDATA CACHE READS RETENTION ENABLE STORAGE IN ROW),
LOB (T_FOOTER)
STORE AS (TABLESPACE LOBDATA CACHE READS RETENTION ENABLE STORAGE IN ROW);I need to export this table and do an import on a different instance.
I know for sure that the tablespace LOBDATA exists on both database but I can't say the same for the user default tablespace.
The problem is that when I import this table, the statement fail because the default tablespace of the user hasn't the same name of the tablespace where the table was exported.
IMP-00003: ORACLE error 959 encountered
ORA-00959: tablespace 'USERWNSTARTUP' does not exist
This because the create table generated by the export has this storage clause:
PCTFREE 10 PCTUSED 40 INITRANS 1 MAXTRANS 255 STORAGE(
INITIAL 65536 FREELISTS 1 FREELIST GROUPS 1) TABLESPACE USERWNSTARTUP LOGGING NOCOMPRESS LOB (B_LOGO) STORE AS (TABLESPACE "LOBDATA" ENABLE STORAGE IN ROW CHUNK 8192 PCTVERSION 10 CACHE READS STORAGE(INITIAL 65536 FREELISTS 1 FREELIST GROUPS 1)
On other tables, where I havent defined any storage clause all works fine.
Is there a way to resolve this problem?
Thanks
Regards

if someone is interested I've found this on the official import oracle documentation:
if the tablespace no longer exists or the user does not have the necessary quota, the system uses the default tablespace for that user as long as the table is unpartitioned, contains no LOB or VARRAY columns, is not a type table, and is not an index-only table with an overflow segment.In my case I've a LOB column, so tablespace information would be exporterd. I've done a trace of the import and I can confirm that on table without lob, varray etc.. the create table statement hasn't the tablespace specification.

Syntax of create table in table management

I am getting error while creating table using storage clause and block utilisation parameters.

Hi,
These very much basics.. Refer to google or ORACLE.com where you find the links.. :-)
Refer to link
http://download-uk.oracle.com/docs/cd/B10501_01/server.920/a96521/tables.htm
Post the Error what you are facing and elaborate what your problem or re-phrase the question so that it will
be easy for us to solve your Issue.
- Pavan Kumar N

Physical attributes for index on temp tables (using physical model)

I need create index on temp tables.
When I generate DDL, it includes physical attributes like ‘LOGGING NOCOMPRESS NOPARALLEL’.
I get error "ORA – 14451 (unsupported feature w/temporary tables)"
I’ve to use physical model in OSDM. How do I get rid of physical attributes in DDL for index?

Hi,
Thanks for reporting this problem.
You can remove the LOGGING clause by opening the Properties dialog for the Index in the Physical model and setting its Logging property to the blank option.
However it's not possible to suppress the NOCOMPRESS and NOPARALLEL at the moment.
I've logged a bug on this.
As a workaround, you could do a global edit on the DDL file to remove all instances of NOCOMPRESS and NOPARALLEL.
David

Trying to create table using Union All Clause with multiple Select stmts

The purpose of the query is to get the Substring from the value for eg.
if the value is *2 ASA* then it should come as ASA
where as if the value is *1.5 TST* the it sholud come as TST like wise for others too.
I am trying to execute the below written SQL stmt but getting error as:
*"ORA-00998 must name this expression with the column alias 00998.00000 - Must name this expression with the column alias"*
CREATE TABLE TEST_CARE AS
SELECT row_id, old_care_lvl,SUBSTR(old_care_lvl,3), len FROM test_care_lvl
WHERE LENGTH(old_care_lvl) =5
UNION ALL
SELECT row_id, old_care_lvl,SUBSTR(old_care_lvl,3), len FROM test_care_lvl
WHERE LENGTH(old_care_lvl) =7
UNION ALL
SELECT row_id, old_care_lvl,SUBSTR(old_care_lvl,3), len FROM test_care_lvl
WHERE LENGTH(old_care_lvl) =14
UNION ALL
SELECT row_id, old_care_lvl,SUBSTR(old_care_lvl,3),LEN FROM test_care_lvl
WHERE LENGTH(old_care_lvl) =7 AND old_care_lvl ='Regular'
I want to create the table using the above given multiple select using the Union ALL clause but when trying to create run the query getting error as "ORA-00998 must name this expression with the column alias 00998.00000 - Must name this expression with the column alias"
Please guide me how to approach to resolve this problem.
Thanks in advance.

When you create a table using a SELECT statement the column names are derived from the SELECT list.
Your problem is that one of your columns is an expression that does not work as a column name SUBSTR(old_care_lvl,3)What you need to do is alias this expression and the CREATE will pick up the alias as the column name, like this:
CREATE TABLE TEST_CARE AS
SELECT row_id, old_care_lvl,SUBSTR(old_care_lvl,3) column3, len FROM test_care_lvl
WHERE LENGTH(old_care_lvl) =5
UNION ALL
SELECT row_id, old_care_lvl,SUBSTR(old_care_lvl,3), len FROM test_care_lvl
WHERE LENGTH(old_care_lvl) =7
UNION ALL
SELECT row_id, old_care_lvl,SUBSTR(old_care_lvl,3), len FROM test_care_lvl
WHERE LENGTH(old_care_lvl) =14
UNION ALL
SELECT row_id, old_care_lvl,SUBSTR(old_care_lvl,3),LEN FROM test_care_lvl
WHERE LENGTH(old_care_lvl) =7 AND old_care_lvl ='Regular'
);You may not like the name "column3" so use something appropriate.

Confusion on nologging clause - for create table

hi guys,
just 1 simple question.
q1) when i create a table via no logging, is the CREATION of the table not logged as well ?
Regards,
Noob

OracleWannabe wrote:
q1) when i create a table via no logging, is the CREATION of the table not logged as well ?If the table is created empty (as in not using a create table as select or CTAS) then there is no difference in the create step. The difference between LOGGING and NOLOGGING takes place for direct path operations.
The Oracle Docs give a very good explanation:
http://download.oracle.com/docs/cd/B28359_01/server.111/b28313/usingpe.htm#i1009116
Regards,
Greg Rahn
http://structureddata.org

ORA-14189: this physical attribute may not be specified for an index subpar

Hi,
I have many partition table and their subpartition and also I create index partition ans index subpartition.
I moved partition table another new tablespace and then when I rebuild partition indexes I am getting below error.
ORA-14189: this physical attribute may not be specified for an index subpartition
I coulsn't understand the problem and I also not find a answer google.
Details:
ALTER INDEX ADMINISTRATOR.DX_IND REBUILD
SUBPARTITION SYS_SUBP148ALTER INDEX ADMINISTRATOR.DX_IND REBUILD
SUBPARTITION SYS_SUBP1ALTER INDEX ADMINISTRATOR.DX_IND REBUILD
SUBPARTITION SYS_SUBP21ALTER INDEX ADMINISTRATOR.DX_IND REBUILD
SUBPARTITION SYS_SUBP41ALTER INDEX ADMINISTRATOR.DX_IND REBUILD
SUBPARTITION SYS_SUBP61ALTER INDEX ADMINISTRATOR.DX_IND REBUILD
SUBPARTITION SYS_SUBP62ALTER INDEX ADMINISTRATOR.DX_IND REBUILD
SUBPARTITION SYS_SUBP63ALTER INDEX ADMINISTRATOR.DX_IND REBUILD
SUBPARTITION SYS_SUBP64ALTER INDEX ADMINISTRATOR.DX_IND REBUILD
SUBPARTITION SYS_SUBP122ALTER INDEX ADMINISTRATOR.DX_IND REBUILD
SUBPARTITION SYS_SUBP123ALTER INDEX ADMINISTRATOR.DX_IND REBUILD
SUBPARTITION SYS_SUBP124ALTER INDEX ADMINISTRATOR.DX_IND REBUILD
SUBPARTITION SYS_SUBP125ALTER INDEX ADMINISTRATOR.DX_IND REBUILD
SUBPARTITION SYS_SUBP201ALTER INDEX ADMINISTRATOR.DX_IND REBUILD
SUBPARTITION SYS_SUBP206ALTER INDEX ADMINISTRATOR.DX_IND REBUILD
SUBPARTITION SYS_SUBP207ALTER INDEX ADMINISTRATOR.DX_IND REBUILD
SUBPARTITION SYS_SUBP208ALTER INDEX ADMINISTRATOR.DX_IND REBUILD
SUBPARTITION SYS_SUBP261ALTER INDEX ADMINISTRATOR.DX_IND REBUILD
SUBPARTITION SYS_SUBP262
Error at line 2
ORA-14189: this physical attribute may not be specified for an index subpartition
db version: 9.2.0.8
Could you any body help me please how can I solve this problem.
thanks and regards,

Hi Justen,
I just run rebuild the index with TOAD. So just I copied toad error output so I haven't written it and also in my computer there is a space. I think when I paste the output here, space gone out.
Anyway, I found workaround solution. First I am taking the script from toad then drop and recreate the index. But this takes very long time, only one index takes 1 hour for recreation. so I have so many index like this and If I calculate all indexes takes 3 days for recreation again.
any other solution is there?
thanks and regards

Creation of new table with attributes of another ??

how can i create a new table which has the same attributes as another ? Please note that the records/tuples in the already existing table shouldn't be copied into the new table.
Illustration:
Table Employee_Details with attributes/fields Name and IDno is present.
A new table Supervisor should have the same attributes/fields Name and IDno.
But the data in Employee_Details table shouldn't be copied into this table (Supervisor).
Can anyone write a query in SQL that does the same i.e. use the attributes of another table during the creation of a new one?
Also can anyone explain why the following query is erroneous ?
sql> create table supervisor as (desc employee_details);
Thanks for your help!

create table new_table as select * from old_table
where 0=1;This statement doesn't create the new_table in the same tablespace than old_table... to take for example only the tablespace, but that's right for storage clause too.
Assuming TITI is my old table, and TOTO my new table :
SQL> show user
USER is "H89UCBAC"
SQL> select default_tablespace from dba_users where username='H89UCBAC';
DEFAULT_TABLESPACE
PSDEFAULT
SQL> create table titi(coltiti number) tablespace tools;
Table created.
SQL> create table toto as select * from titi;
Table created.
SQL> ed
Wrote file afiedt.buf
1* select table_name,tablespace_name from dba_tables where table_name in ('TITI','TOTO')
SQL> /
TABLE_NAME                     TABLESPACE_NAME
TOTO                           PSDEFAULT
TITI                           TOOLS
SQL>   1* select replace(dbms_metadata.get_ddl('TABLE','TITI'),'TITI','TOTO') from dual
SQL> /
REPLACE(DBMS_METADATA.GET_DDL('TABLE','TITI'),'TITI','TOTO')
CREATE TABLE "H89UCBAC"."TOTO"
   (    "COLTOTO" NUMBER
   ) PCTFREE 10 PCTUSED 40 INITRANS 1 MAXTRANS 255 NOCOMPRESS LOGGING
STORAGE(INITIAL 65536 NEXT 65536 MINEXTENTS 1 MAXEXTENTS 2147483645
PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT)
TABLESPACE "TOOLS"
SQL> drop table toto;
Table dropped.
SQL> CREATE TABLE "H89UCBAC"."TOTO"
2   (    "COLTOTO" NUMBER
3   ) PCTFREE 10 PCTUSED 40 INITRANS 1 MAXTRANS 255 NOCOMPRESS LOGGING
4 STORAGE(INITIAL 65536 NEXT 65536 MINEXTENTS 1 MAXEXTENTS 2147483645
5 PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT)
6 TABLESPACE "TOOLS"
7 /
Table created.
SQL> select table_name,tablespace_name from dba_tables where table_name in ('TITI','TOTO');
TABLE_NAME                     TABLESPACE_NAME
TITI                           TOOLS
TOTO                           TOOLS
SQL> HTH,
Nicolas.
Message was edited by:
N. Gasparotto

Syntax error in creating table

Could some one plz help me as to what is wrong in creating below table structure:
create table test as (select * from schema.tablename where 1=2)
TABLESPACE PCR_ARCHIVE_DATA_04
PCTUSED 0
PCTFREE 10
INITRANS 1
MAXTRANS 255
STORAGE (
INITIAL 64K
MINEXTENTS 1
MAXEXTENTS UNLIMITED
PCTINCREASE 0
BUFFER_POOL DEFAULT
NOLOGGING
COMPRESS
NOCACHE
PARALLEL ( DEGREE 6 INSTANCES 1 )
MONITORING;

AS SELECT comes after physical attributes, like
create table test TABLESPACE PCR_ARCHIVE_DATA_04
PCTUSED 0
PCTFREE 10
INITRANS 1
MAXTRANS 255
STORAGE (
INITIAL 64K
MINEXTENTS 1
MAXEXTENTS UNLIMITED
PCTINCREASE 0
BUFFER_POOL DEFAULT
NOLOGGING
COMPRESS
NOCACHE
PARALLEL ( DEGREE 6 INSTANCES 1 )
MONITORING
as (select * from schema.tablename where 1=2)Best regards
Maxim

Dynamically create Table partition

Hi all,
Anybody having script to add partition to a table using plsql.My requirment is to create partition for every month ( time_id , from time attribute table ) dynamically.
Thanks in Advance
Ramesh K C R

Just build you SQL statement to create partition in a VARCHAR2 variable
and use EXECUTE IMMEDIATE to run it.
Take care to have been granted directly privileges to run CREATE TABLE, ALTER TABLE (not through a role) or create you code with AUTHID CURRENT_USER clause.

Create a dynamic attribute for each user

Hi All,
I request you all to let me know how to give an approach to the following requirement.
REQUIREMENT: I have to create a dynamic attribute in UME for each user and the read the attribute on lead selection of a table having list of Users.
 On lead selection, the dynamic attribute value should be either true or false. Based on this value the rest of the application specific operations wil be taken care.
 If a particular User does not have the dynamic attribute associated to it, then we need to create the same.
Looking forwarrd for your help.
Regards
Dipendra

//@@begin javadoc:UMSavePropertiesByNode()
 /** Declared method. */
//@@end
public boolean UMSavePropertiesByNode( )
 //@@begin UMSavePropertiesByNode()
 try {
 if (wdContext.currentUserDataElement().getVaIUserMaint().setAttribute("com.sap.security.core.usermanagement", this.getUMPropertyName(null) + ".TableColumns", this.getPropertiesByNode())) {
 wdContext.currentUserDataElement().getVaIUserMaint().save();
 wdContext.currentUserDataElement().getVaIUserMaint().commit();
 msg.reportMessage(IMessageTableUtilsComponent.UMPROPERTY__SAVE__FIELDS__SUCCESS, null, false);
 } catch (UMException ex) {
 wdContext.currentUserDataElement().getVaIUserMaint().rollback();
 msg.reportMessage(IMessageTableUtilsComponent.UMPROPERTY__SAVE__FIELDS__ERROR, null, false);
 return false;
 return true;
 //@@end
//@@begin javadoc:UMLoadFieldsProperties()
 /** Declared method. */
//@@end
public petrobras.com.br.classes.FieldsTable UMLoadFieldsProperties( petrobras.com.br.classes.FieldsTable fields )
 //@@begin UMLoadFieldsProperties()
 String properties[] = wdContext.currentUserDataElement().getVaIUserMaint().getAttribute("com.sap.security.core.usermanagement", this.getUMPropertyName(null) + ".TableColumns");
 if (Compare.getLenght(properties) > 0) {
 //msg.reportWarning("[UMLoadFieldsProperties]: properties.length = " + properties.length);
 for (int i = 0; i < properties.length; i++) {
 int attrPos = Integer.parseInt(properties.substring(properties.indexOf("(") + 1, properties.indexOf(")")));
 String attrName = (String) properties.substring(properties.indexOf(")") + 1, properties.indexOf("="));
 int attrValue = Integer.parseInt(properties.substring(properties.indexOf("=") + 1, properties.indexOf(";")));
 Field item = fields.getField(attrName);
 if (item != null) {
 item.setPosition(attrPos);
 item.setVisibility(WDVisibility.valueOf(attrValue));
 fields.removeFieldByName(attrName);
 fields.addField(item);
 return fields;
 //@@end
regards,
Angelo

How to specify tablespace for a primary key inde in create table statement

How to specify the tablespace for a primary key index in a create table statement?
Does the following statement is right?
CREATE TABLE 'GPS'||TO_CHAR(SYSDATE+1,'YYYYMMDD')
            ("ID" NUMBER(10,0) NOT NULL ENABLE,
            "IP_ADDRESS" VARCHAR2(32 BYTE),
            "EQUIPMENT_ID" VARCHAR2(32 BYTE),
            "PACKET_DT" DATE,
            "PACKET" VARCHAR2(255 BYTE),
            "PACKET_FORMAT" VARCHAR2(32 BYTE),
            "SAVED_TIME" DATE DEFAULT CURRENT_TIMESTAMP,
             CONSTRAINT "UDP_LOG_PK" PRIMARY KEY ("ID") TABLESPACE "INDEX_DATA"
             TABLESPACE "SBM_DATA";   Thank you
Edited by: qkc on 09-Nov-2009 13:42

As orafad indicated, you'll have to use the USING INDEX clause from the documentation, i.e.
SQL> ed
Wrote file afiedt.buf
1 CREATE TABLE GPS
2              ("ID" NUMBER(10,0) NOT NULL ENABLE,
3              "IP_ADDRESS" VARCHAR2(32 BYTE),
4              "EQUIPMENT_ID" VARCHAR2(32 BYTE),
5              "PACKET_DT" DATE,
6              "PACKET" VARCHAR2(255 BYTE),
7              "PACKET_FORMAT" VARCHAR2(32 BYTE),
8              "SAVED_TIME" DATE DEFAULT CURRENT_TIMESTAMP,
9               CONSTRAINT "UDP_LOG_PK" PRIMARY KEY ("ID") USING INDEX TABLESP
ACE "USERS"
10               )
11*              TABLESPACE "USERS"
SQL> /
Table created.Justin

Create table in Database Under Creating Direct Database Request in Answers

When creating the table, I got the following error:
State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 43093] An error occurred while processing the EXECUTE PHYSICAL statement. [nQSError: 17001] Oracle Error code: 955, message: ORA-00955: name is already used by an existing object at OCI call OCIStmtExecute: CREATE TABLE AGG_PRODUCTS_CATEGORY_D AS (SELECT DISTINCT PROD_CATEGORY_ID ,PROD_CATEGORY ,PROD_TOTAL_ID ,PROD_TOTAL FROM PRODUCTS) . [nQSError: 17011] SQL statement execution failed. (HY000)
SQL Issued: EXECUTE PHYSICAL CONNECTION POOL "SH"."Connection Pool" CREATE TABLE AGG_PRODUCTS_CATEGORY_D AS (SELECT DISTINCT PROD_CATEGORY_ID ,PROD_CATEGORY ,PROD_TOTAL_ID ,PROD_TOTAL FROM PRODUCTS)
SQL Statement:
CREATE TABLE AGG_PRODUCTS_CATEGORY_D
AS
(SELECT DISTINCT PROD_CATEGORY_ID
,PROD_CATEGORY
,PROD_TOTAL_ID
,PROD_TOTAL
FROM PRODUCTS);
Connection Pool: "SH"."Connection Pool"
The above sql statement works when creating the table in SQLPlus. Is there a syntax error when trying to do it in Answers? I don't use the semi-colon at the end in Answers. Thanks.
Edited by: whoknows on May 24, 2010 1:55 PM

look at your physical layer in the RPD you'll find that the does table exist (easy to find, it's represented by an icon in red) and you need to drop it before running your aggregate.
Fiston

An error occured while creating the original attribute for message no26 296

Hi All,
I am new to DMS , we are trying to store PM documents on content server , created a storage category and while assigning files to storage category then on saving the document i get the below error :
An error occured while creating the original attribute for
Message no. 26 296
Diagnosis
An error occured while creating an original in the Knowledge Provider.
System Response
The original could not be created.
Procedure
Contact the systems administrator and check the log file (transaction Evaluate application log, object SDOK).
Please let me know what configs i am missing ...
Thanks in advance
regrds
pushpa

Hi Pushpa,
Which enhancement package are you on currently? This is observed in cases where originals in DIR's are invisible and sometimes error message 26296 occurs in transaction CV01n. Hence,please check your entries in the table SDOKPROP to avoid such a problem in your system.
Further,suggest you explore if the below resolutions can be adopted in your case.
http://wiki.sdn.sap.com/wiki/pages/viewpage.action?pageId=10321987
http://wiki.sdn.sap.com/wiki/display/PLM/OriginalsinvisibleafterEHP3or+EHP4
Regards,
Pradeepkumar haragoldavar

Create table Physical attributes clause

Similar Messages

Maybe you are looking for