Temp tablespace grow too big???

we have EBS R12.1 on LINUX X86_64 with ORACLE database version 11.1.0.7. every week we have temporary tablespace grow too big (> 32 GB) and out of extent.
Based on our research some some sql statement or report cause this issue. if we 'analyze stratistics", most time problem can fix. It cause us some time need run "analyze statistics" several times in one day.
Does anyone have solution for this?
Thanks.

Please see if these docs help.
Temporary Segments: What Happens When a Sort Occurs [ID 102339.1]
Queries to monitor Temporary Tablespace usage [ID 289894.1]
How Can Temporary Segment Usage Be Monitored Over Time? [ID 364417.1]
Thanks,
Hussein

Similar Messages

  • PcSync2.SML file grows too big with Outlook calend...

    My problem is that file PcSync2.SML grows way too big when I am synchronizing Outlook calendar information with my N95 phone. In first synchronization time PcSync2.SML file size is about 8MB, second synchronization gives additional 3MB, altogether ~11MB even tough I just synchronize calendar items one week past and one week to the future. Can somebody explain why file size of PcSync2.SML is so ridiculous?
    This is big problem for me, because our company has limited profile space to 30Mb and I am running out of that right from the start. This is global setting for our company and can not be changed.
    PC Suite version: 6.84.10.3
    Windows: Windows XP Professional 2002, SP2
    Connection method: Cable
    I would be really grateful of answers how to solve this problem.

    PC Suite releases including and after 6.85, contained some changes to reduce the size of the PC Sync control file. It is still possible, however, in very restricted environments, that this file could grow beyond the size limit.
    Further changes are being considered that would allow Administrative control of the location of the control file, such that a less restricted location could be selected.

  • Temp tablespace - why so big?

    Temp tablespace (size 6gb) is twice the size of my data and index tablespace combined. I am running into space issues and am wondering is it possible to resize this tablespace and/or take some other action to prevent the temp tablespace getting so relatively large?
    Thanks in advance.

    The Temporary Tablespace holds only 1 Temporary Segment shared all by all user sessions. Each session takes one or more extents. When a session finishes its operation, it "releases" the extent it used for use by another session but the size of the Segment does NOT shrink.
    Therefore, the Segment would grow to the peak concurrent temporary extent usage -- eg at some point in time, if you had 4 very large queries running concurently taking up 8GB then the segment would have grown to 8GB. However, even if you never have such concurrent usage (for example the normal load is for 20 users concurrently taking up 500MB only !), the segment remains at 8GB.
    In some environments, the Temporary tablespace could grow during periodic (say Monthly Reporting) batch jobs after which it is dropped and recreated again.
    This segment is used not just for "SORT" operations. It is also used for HASH JOIN overflows to disk and also for SORT MERGE operations.
    You can monitor the size of the segment in V$SORT_SEGMENT. You can monitor users currently using it in V$SORT_USAGE or V$TEMPSEG_USAGE.
    Hemant K Chitale
    http://hemantoracledba.blogpsot.com

  • Tablespace Index too big

    Hi,
    I have a BBDD and i have one tablespace for Data and one Tablespace for Indexes. My problem is that my tablespace for indexes is too big. it is longer that tablespace Data, but it is not normal.
    The tablespace of index dont use all space.
    Can i rebuld the tablespace index?
    Why grew the tablespace index more than tablespace data?

    Its quite difficult to tell you the exact reason without knowing much from your side.
    However, try rebuilding indexes into new tablespace and drop the old one.
    Jaffar

  • EBS Database R12.1 temporary tablespace grow too quick??

    we have a EBS R12.1 database on Redhat LINUX server. Recently this database every day Temporary tablespace grow at least 1 GB. This database temporary tablespace (with two temp files) has been grow to 45 GB.
    Does anyone know what wrong?
    How to fix problem?

    I eventually figure out this temporary tablespace grow is cause by OEM.
    SQL statement is:
    /* OracleOEM */ SELECT end_time, status, session_key, session_recid, session_stamp, command_id, start_time, time_taken_
    display, input_type, output_device_type, input_bytes_display, output_bytes_display, output_bytes_per_sec_display
    FROM (SELECT end_time, status, session_key, session_recid, session_stamp, command_id, start_time,
    time_taken_display, input_type, output_device_type, input_bytes_display, output_bytes_di
    splay, output_bytes_per_sec_display FROM v$rman_backup_job_details ORDER BY end_time DESC) WHERE rownum
    = 1;
    ANyone know why this statement will take 30GB temporary space on EBS R12.1?
    Thanks.

  • SYSAUX tablespace grow too quick????

    We have EBS R12.1 on LINUX system. Recently I found our development EBS database SYSAUX tablespace grow very quick. The SYSAUX tablespace has two data files and each data files size is 6GB (total 12 GB). In one month all 12 GB space are gone.
    My questions are:
    1. what objects or reports or ??? take this much space?
    2. how to delete un-need space?
    3. what is reasonable SYSAUX size?
    Thanks.

    I double check SYSAUX space usage and found it only use less than 100MB. Why SYSAUX show all 12 Gb space are gone?
    SQL> l
    1 SELECT occupant_name, schema_name, move_procedure,
    2 space_usage_kbytes
    3 FROM v$sysaux_occupants
    4* ORDER BY 1
    SQL> /
    OCCUPANT_NAME SCHEMA_NAME MOVE_PROCEDURE SPACE_USAGE_KBYTES
    AO SYS DBMS_AW.MOVE_AWMETA 45888
    AUTO_TASK SYS 320
    EM SYSMAN emd_maintenance.move_em_tblspc 0
    EM_MONITORING_USER DBSNMP 0
    EXPRESSION_FILTER EXFSYS 0
    JOB_SCHEDULER SYS 1152
    LOGMNR SYSTEM SYS.DBMS_LOGMNR_D.SET_TABLESPACE 13376
    LOGSTDBY SYSTEM SYS.DBMS_LOGSTDBY.SET_TABLESPACE 1600
    ORDIM ORDSYS 0
    ORDIM/PLUGINS ORDPLUGINS 0
    ORDIM/SQLMM SI_INFORMTN_SCHEMA 0
    PL/SCOPE SYS 640
    SDO MDSYS MDSYS.MOVE_SDO 0
    SM/ADVISOR SYS 198528
    SM/AWR SYS 1006144
    SM/OPTSTAT SYS 10866560
    SM/OTHER SYS 8192
    SMON_SCN_TIME SYS 3328
    SQL_MANAGEMENT_BASE SYS 1728
    STATSPACK PERFSTAT 0
    STREAMS SYS 1216
    TEXT CTXSYS DRI_MOVE_CTXSYS 0
    TSM TSMSYS 256
    ULTRASEARCH WKSYS MOVE_WK 0
    ULTRASEARCH_DEMO_USE WK_TEST MOVE_WK 0
    R
    WM WMSYS DBMS_WM.move_proc 0
    XDB XDB XDB.DBMS_XDB.MOVEXDB_TABLESPACE 56192
    XSAMD OLAPSYS DBMS_AMD.Move_OLAP_Catalog 0
    XSOQHIST SYS DBMS_XSOQ.OlapiMoveProc 45888
    29 rows selected.

  • Tablespace growing too large

    Good morning gurus,
    Sorry if I sound novice at some point .
    I have this table space vending of size 188,598.6MB.It keeps on growing.I have to give it extra space every week and all is consumed.It is a permanent table space with extent management local and segment space management auto.This table space is the backbone of the database which is 250G.We are currently running oracle 10.2.0.4 on windows.
    Please help
    Regards
    Deepika

    Hi..
    Please do mention the database version and the OS.
    You need to know what are the objects, object_types on such a big tablespace.Which schemas use it waht do they do.Do they do any kind of DIRECT Loading in the database.Are all the tables and the indexes on the same tablespace.What i feel is, you are having all the tables and the indexes on the same tablespace.I would recommend 2 things:--
    1. Do the data purging.Talk to the considered applications team,or who so ever is the concerned person, and the decide data retention period in the database and move the rest of the data to some other database as history.
    2. Keep different tablespaces for the tables and indexes.
    HTH
    Anand

  • Log file is growing too big and too quick on ECC6 EHP4 system

    Hello there,
    i have ECC6EHP6 system based on NW 7.01 and MSSQL as back-end.
    My log file is growing very fast. i seen a number of threads but does not got some perfect idea what to do. Please see DEV_RFC0 and DEV_W0 log file excerpt below. Please help
    DEV_RFC0
    Trace file opened at 20100618 065308 Eastern Daylight Time, SAP-REL 701,0,14 RFC-VER U 3 1016574 MT-SL
    ======> CPIC-CALL: 'ThSAPOCMINIT' : cmRc=2 thRc=679
    Transaction program not registered                                      
    ABAP Programm: SAPLSADC (Transaction: )
    User: DDIC (Client: 000)
    Destination: SAPDB_DBM_DAEMON (handle: 2, , )
    SERVER> RFC Server Session (handle: 1, 59356166, {ADC77ADF-C575-F1CC-B797-0019B9E204CC})
    SERVER> Caller host:
    SERVER> Caller transaction code:  (Caller Program: SAPLSADC)
    SERVER> Called function module: DBM_CONNECT_PUR
    Error RFCIO_ERROR_SYSERROR in abrfcpic.c : 1501
    CPIC-CALL: 'ThSAPOCMINIT' : cmRc=2 thRc=679
    Transaction program not registered                                      
    DEST =SAPDB_DBM_DAEMON
    HOST =%%RFCSERVER%%
    PROG =dbmrfc@sapdb
    Trace file opened at 20100618 065634 Eastern Daylight Time, SAP-REL 701,0,14 RFC-VER U 3 1016574 MT-SL
    ======> CPIC-CALL: 'ThSAPOCMINIT' : cmRc=2 thRc=679
    Transaction program not registered                                      
    ABAP Programm: SAPLSADC (Transaction: )
    User: DDIC (Client: 000)
    Destination: SAPDB_DBM_DAEMON (handle: 2, , )
    SERVER> RFC Server Session (handle: 1, 59587535, {28C87ADF-4577-F16D-B797-0019B9E204CC})
    SERVER> Caller host:
    SERVER> Caller transaction code:  (Caller Program: SAPLSADC)
    SERVER> Called function module: DBM_CONNECT_PUR
    Error RFCIO_ERROR_SYSERROR in abrfcpic.c : 1501
    CPIC-CALL: 'ThSAPOCMINIT' : cmRc=2 thRc=679
    Transaction program not registered                                      
    DEST =SAPDB_DBM_DAEMON
    HOST =%%RFCSERVER%%
    PROG =dbmrfc@sapdb
    DEV_W0
    X 
    X Fri Jun 18 18:05:15 2010
    X  *** ERROR => EmActiveData: Invalid Context Handle -1 [emxx.c       2214]
    X  *** ERROR => EmActiveData: Invalid Context Handle -1 [emxx.c       2214]
    N 
    N Fri Jun 18 18:05:25 2010
    N  RSEC: The entry with identifier /RFC/DIICLNT800
    N  was encrypted by a system
    N  with different SID and cannot be decrypted here.
    N  RSEC: The entry with identifier /RFC/T90CLNT090
    N  was encrypted by a system
    N  with different SID and cannot be decrypted here.
    X 
    X Fri Jun 18 18:05:39 2010
    X  *** ERROR => EmActiveData: Invalid Context Handle -1 [emxx.c       2214]
    X  *** ERROR => EmActiveData: Invalid Context Handle -1 [emxx.c       2214]
    X 
    X Fri Jun 18 18:05:46 2010
    X  *** ERROR => EmActiveData: Invalid Context Handle -1 [emxx.c       2214]
    X  *** ERROR => EmActiveData: Invalid Context Handle -1 [emxx.c       2214]
    X 
    X Fri Jun 18 18:05:52 2010
    X  *** ERROR => EmActiveData: Invalid Context Handle -1 [emxx.c       2214]
    X  *** ERROR => EmActiveData: Invalid Context Handle -1 [emxx.c       2214]
    X 
    N Sun Jun 20 10:55:32 2010
    N  RSEC: The entry with identifier /RFC/DIICLNT800
    N  was encrypted by a system
    N  with different SID and cannot be decrypted here.
    N  RSEC: The entry with identifier /RFC/T90CLNT090
    N  was encrypted by a system
    N  with different SID and cannot be decrypted here.
    X 
    X Sun Jun 20 11:00:02 2010
    X  *** ERROR => EmActiveData: Invalid Context Handle -1 [emxx.c       2214]
    N 
    N Sun Jun 20 11:00:32 2010
    N  RSEC: The entry with identifier /RFC/DIICLNT800
    N  was encrypted by a system
    N  with different SID and cannot be decrypted here.
    N  RSEC: The entry with identifier /RFC/T90CLNT090
    N  was encrypted by a system
    N  with different SID and cannot be decrypted here.
    C 
    C Sun Jun 20 11:03:34 2010
    C  Thread ID:1956
    C  dbmssslib.dll patch info
    C    patchlevel   0
    C    patchno      13
    C    patchcomment Errors when running with par_stmt_prepare set to zero (1253696)
    C  Local connection used on SAPFIVE to named instance: np:SAPFIVE\ECT
    C 
    C Sun Jun 20 11:03:49 2010
    C  OpenOledbConnection: line 23839. hr: 0x8000ffff Login timeout expired
    C  sloledb.cpp [OpenOledbConnection,line 23839]: Error/Message: (err 0, sev 0), Login timeout expired
    C  Procname: [OpenOledbConnection - no proc]
    C  sloledb.cpp [OpenOledbConnection,line 23839]: Error/Message: (err -1, sev 0), An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.
    C  Procname: [OpenOledbConnection - no proc]
    C  sloledb.cpp [OpenOledbConnection,line 23839]: Error/Message: (err -1, sev 0), SQL Network Interfaces: Server doesn't support requested protocol [xFFFFFFFF].
    C  Procname: [OpenOledbConnection - no proc]
    C  sloledb.cpp [OpenOledbConnection,line 23839]: Error/Message: (err 0, sev 0), Invalid connection string attribute
    C  Procname: [OpenOledbConnection - no proc]
    C 
    C Sun Jun 20 11:04:04 2010
    C  OpenOledbConnection: line 23839. hr: 0x8000ffff Login timeout expired
    C  sloledb.cpp [OpenOledbConnection,line 23839]: Error/Message: (err 0, sev 0), Login timeout expired
    C  Procname: [OpenOledbConnection - no proc]
    C  sloledb.cpp [OpenOledbConnection,line 23839]: Error/Message: (err -1, sev 0), An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.
    C  Procname: [OpenOledbConnection - no proc]
    C  sloledb.cpp [OpenOledbConnection,line 23839]: Error/Message: (err -1, sev 0), SQL Network Interfaces: Server doesn't support requested protocol [xFFFFFFFF].
    C  Procname: [OpenOledbConnection - no proc]
    C  sloledb.cpp [OpenOledbConnection,line 23839]: Error/Message: (err 0, sev 0), Invalid connection string attribute
    C  Procname: [OpenOledbConnection - no proc]
    C 
    C Sun Jun 20 11:04:19 2010
    C  OpenOledbConnection: line 23839. hr: 0x8000ffff Login timeout expired
    C  sloledb.cpp [OpenOledbConnection,line 23839]: Error/Message: (err 0, sev 0), Login timeout expired
    C  Procname: [OpenOledbConnection - no proc]
    C  sloledb.cpp [OpenOledbConnection,line 23839]: Error/Message: (err -1, sev 0), An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.
    C  Procname: [OpenOledbConnection - no proc]
    C  sloledb.cpp [OpenOledbConnection,line 23839]: Error/Message: (err -1, sev 0), SQL Network Interfaces: Server doesn't support requested protocol [xFFFFFFFF].
    C  Procname: [OpenOledbConnection - no proc]
    C  sloledb.cpp [OpenOledbConnection,line 23839]: Error/Message: (err 0, sev 0), Invalid connection string attribute
    C  Procname: [OpenOledbConnection - no proc]
    C  failed to establish conn to np:SAPFIVE\ECT.
    C  Retrying without protocol specifier: SAPFIVE\ECT
    C  Connected to db server : [SAPFIVE\ECT] server_used : [SAPFIVE\ECT], dbname: ECT, dbuser: ect
    C  pn_id:SAPFIVE_ECT_ECTECT_ECT
    B  Connection 4 opened (DBSL handle 2)
    B  Wp  Hdl ConName          ConId     ConState     TX  PRM RCT TIM MAX OPT Date     Time   DBHost         
    B  000 000 R/3              000000000 ACTIVE       YES YES NO  000 255 255 20100618 061458 SAPFIVE\ECT    
    B  000 001 +DBO+0050      000002156 INACTIVE     NO  NO  NO  004 255 255 20100618 101017 SAPFIVE\ECT    
    B  000 002 +DBO+0050      000001981 DISCONNECTED NO  NO  NO  000 255 255 20100620 070023 SAPFIVE\ECT    
    B  000 003 +DBO+0050      000001982 DISCONNECTED NO  NO  NO  000 255 255 20100620 070023 SAPFIVE\ECT    
    B  000 004 R/3*INACT_PACK   000002157 ACTIVE       NO  NO  NO  004 255 255 20100620 110334 SAPFIVE\ECT  
    N Sun Jun 20 17:35:35 2010
    N  RSEC: The entry with identifier /RFC/DIICLNT800
    N  was encrypted by a system
    N  with different SID and cannot be decrypted here.
    N  RSEC: The entry with identifier /RFC/T90CLNT090
    N  was encrypted by a system
    N  with different SID and cannot be decrypted here.
    M 
    M Sun Jun 20 17:47:29 2010
    M  ThAlarmHandler (1)
    M  ThAlarmHandler (1)
    M  ThAlarmHandler: set CONTROL_TIMEOUT/DP_CONTROL_JAVA_EXIT and break sql
    C 
    C Sun Jun 20 17:47:33 2010
    C  SQLBREAK: DBSL_CMD_SQLBREAK: CbOnCancel was not set. rc: 15
    M  program canceled
    M    reason   = max run time exceeded
    M    user     = SAPSYS     
    M    client   = 000
    M    terminal =                    
    M    report   = SAPMSSY2                               
    M  ThAlarmHandler: return from signal handler
    A 
    A Sun Jun 20 17:48:33 2010
    A  TH VERBOSE LEVEL FULL
    A  ** RABAX: level LEV_RX_PXA_RELEASE_MTX entered.
    A  ** RABAX: level LEV_RX_PXA_RELEASE_MTX completed.
    A  ** RABAX: level LEV_RX_COVERAGE_ANALYSER entered.
    A  ** RABAX: level LEV_RX_COVERAGE_ANALYSER completed.
    A  ** RABAX: level LEV_RX_ROLLBACK entered.
    A  ** RABAX: level LEV_RX_ROLLBACK completed.
    A  ** RABAX: level LEV_RX_DB_ALIVE entered.
    A  ** RABAX: level LEV_RX_DB_ALIVE completed.
    A  ** RABAX: level LEV_RX_HOOKS entered.
    A  ** RABAX: level LEV_RX_HOOKS completed.
    A  ** RABAX: level LEV_RX_STANDARD entered.
    A  ** RABAX: level LEV_RX_STANDARD completed.
    A  ** RABAX: level LEV_RX_STOR_VALUES entered.
    A  ** RABAX: level LEV_RX_STOR_VALUES completed.
    A  ** RABAX: level LEV_RX_C_STACK entered.
    A 
    A Sun Jun 20 17:48:42 2010
    A  ** RABAX: level LEV_RX_C_STACK completed.
    A  ** RABAX: level LEV_RX_MEMO_CHECK entered.
    A  ** RABAX: level LEV_RX_MEMO_CHECK completed.
    A  ** RABAX: level LEV_RX_AFTER_MEMO_CHECK entered.
    A  ** RABAX: level LEV_RX_AFTER_MEMO_CHECK completed.
    A  ** RABAX: level LEV_RX_INTERFACES entered.
    A  ** RABAX: level LEV_RX_INTERFACES completed.
    A  ** RABAX: level LEV_RX_GET_MESS entered.
    A  ** RABAX: level LEV_RX_GET_MESS completed.
    A  ** RABAX: level LEV_RX_INIT_SNAP entered.
    A  ** RABAX: level LEV_RX_INIT_SNAP completed.
    A  ** RABAX: level LEV_RX_WRITE_SYSLOG entered.
    A  ** RABAX: level LEV_RX_WRITE_SYSLOG completed.
    A  ** RABAX: level LEV_RX_WRITE_SNAP_BEG entered.
    A  ** RABAX: level LEV_RX_WRITE_SNAP_BEG completed.
    A  ** RABAX: level LEV_RX_WRITE_SNAP entered.
    A 
    A Sun Jun 20 17:48:48 2010
    A  ** RABAX: level LEV_SN_END completed.
    A  ** RABAX: level LEV_RX_WRITE_SNAP_END entered.
    A  ** RABAX: level LEV_RX_WRITE_SNAP_END completed.
    A  ** RABAX: level LEV_RX_SET_ALERT entered.
    A  ** RABAX: level LEV_RX_SET_ALERT completed.
    A  ** RABAX: level LEV_RX_COMMIT entered.
    A  ** RABAX: level LEV_RX_COMMIT completed.
    A  ** RABAX: level LEV_RX_SNAP_SYSLOG entered.
    A  ** RABAX: level LEV_RX_SNAP_SYSLOG completed.
    A  ** RABAX: level LEV_RX_RESET_PROGS entered.
    A  ** RABAX: level LEV_RX_RESET_PROGS completed.
    A  ** RABAX: level LEV_RX_STDERR entered.
    A  Sun Jun 20 17:48:48 2010
    A 
    A  ABAP Program SAPMSSY2                                .
    A  Source RSBTCTRC                                 Line 131.
    A  Error Code TIME_OUT.
    A  Module  $Id: //bas/701_REL/src/krn/runt/abinit.c#1 $ SAP.
    A  Function ab_chstat Line 1941.
    A  ** RABAX: level LEV_RX_STDERR completed.
    A  ** RABAX: level LEV_RX_RFC_ERROR entered.
    A  ** RABAX: level LEV_RX_RFC_ERROR completed.
    A  ** RABAX: level LEV_RX_RFC_CLOSE entered.
    A  ** RABAX: level LEV_RX_RFC_CLOSE completed.
    A  ** RABAX: level LEV_RX_IMC_ERROR entered.
    A  ** RABAX: level LEV_RX_IMC_ERROR completed.
    A  ** RABAX: level LEV_RX_DATASET_CLOSE entered.
    A  ** RABAX: level LEV_RX_DATASET_CLOSE completed.
    A  ** RABAX: level LEV_RX_RESET_SHMLOCKS entered.
    A  ** RABAX: level LEV_RX_RESET_SHMLOCKS completed.
    A  ** RABAX: level LEV_RX_ERROR_SAVE entered.
    A  ** RABAX: level LEV_RX_ERROR_SAVE completed.
    A  ** RABAX: level LEV_RX_ERROR_TPDA entered.
    A  ** RABAX: level LEV_RX_ERROR_TPDA completed.
    A  ** RABAX: level LEV_RX_PXA_RELEASE_RUDI entered.
    A  ** RABAX: level LEV_RX_PXA_RELEASE_RUDI completed.
    A  ** RABAX: level LEV_RX_LIVE_CACHE_CLEANUP entered.
    A  ** RABAX: level LEV_RX_LIVE_CACHE_CLEANUP completed.
    A  ** RABAX: level LEV_RX_END entered.
    A  ** RABAX: level LEV_RX_END completed.
    A  ** RABAX: end no http/smtp
    A  ** RABAX: end RX_BTCHLOG|RX_VBLOG
    A  Time limit exceeded..
    A 
    X 
    X Sun Jun 20 17:49:03 2010
    X  *** ERROR => EmActiveData: Invalid Context Handle -1 [emxx.c       2214]
    N Sun Jun 20 18:35:40 2010
    N  RSEC: The entry with identifier /RFC/DIICLNT800
    N  was encrypted by a system
    N  with different SID and cannot be decrypted here.
    N  RSEC: The entry with identifier /RFC/T90CLNT090
    N  was encrypted by a system
    N  with different SID and cannot be decrypted here.
    N 
    N Sun Jun 20 18:50:35 2010
    N  RSEC: The entry with identifier /RFC/DIICLNT800
    N  was encrypted by a system
    N  with different SID and cannot be decrypted here.
    N  RSEC: The entry with identifier /RFC/T90CLNT090
    N  was encrypted by a system
    N  with different SID and cannot be decrypted here.
    N 
    N Sun Jun 20 18:55:31 2010
    N  RSEC: The entry with identifier /RFC/DIICLNT800
    N  was encrypted by a system
    N  with different SID and cannot be decrypted here.
    N  RSEC: The entry with identifier /RFC/T90CLNT090
    N  was encrypted by a system
    N  with different SID and cannot be decrypted here.
    N 
    N Sun Jun 20 19:00:31 2010
    N  RSEC: The entry with identifier /RFC/DIICLNT800
    N  was encrypted by a system
    N  with different SID and cannot be decrypted here.
    N  RSEC: The entry with identifier /RFC/T90CLNT090
    N  was encrypted by a system
    N  with different SID and cannot be decrypted here.
    X 
    X Sun Jun 20 19:01:59 2010
    X  *** ERROR => EmActiveData: Invalid Context Handle -1 [emxx.c       2214]
    X 
    X Sun Jun 20 19:02:05 2010
    X  *** ERROR => EmActiveData: Invalid Context Handle -1 [emxx.c       2214]
    M 
    M Sun Jun 20 19:04:02 2010
    M  ***LOG R49=> ThReceive, CPIC-Error (020223) [thxxhead.c   7488]
    M  ***LOG R5A=> ThReceive, CPIC-Error (76495728) [thxxhead.c   7493]
    M  ***LOG R64=> ThReceive, CPIC-Error ( CMSEND(SAP)) [thxxhead.c   7498]
    N 
    N Sun Jun 20 19:05:31 2010
    N  RSEC: The entry with identifier /RFC/DIICLNT800
    N  was encrypted by a system
    N  with different SID and cannot be decrypted here.
    N  RSEC: The entry with identifier /RFC/T90CLNT090
    N  was encrypted by a system
    N  with different SID and cannot be decrypted here.
    Thanks
    Mani

    i have few BG jobs running at backend, but i dont think that could be a problem. I have these jobs running
    ESH_IX_PROCESS_CP_20100621051308
    EU_PUT
    EU_REORG
    RPTMC_CREATE_CHANGEPOINT_AUTH
    i cancelled  the last one and first job is for trex indexing for changed object i SAP hR master data. middle two i dont know the purpose.
    do you think these could be problem?
    Mani

  • Changelog.data size growing too big in embedded LDAP /weblogic

    Hi Team,
    We have embedded LDAP.
    We are having issues in setting the no of entries for changelog.data.
    Could anyone of you help as how could we set the treshold for changelog.data .
    we are using Linux server and weblogic as app server.
    Thanks In Advance..

    Thanks..
    But that doesnt seemed to be working.
    I have set following parameter in startup
    -javaagent:/app/platform/wily/current//Agent.jar -Dcom.wily.introscope.agentProfile=/app/platform/wily/current/IntroscopeAgent.profile - Dcom.wily.introscope.agent.agentName=Cramer-Dev0-RM-Admin -Dweblogic.security.ldap.changeLogThreshold=10 -Dweblogic.security.ldap.maxSize=1048576
    Now prior to setting 10 ,I had set it to 30 cleared changelog.data and restarted .It got generated with 28mb size.
    After setting 10 also its the same size of changelog that i could see.
    could you tell me what went wrong..
    Thanks

  • SQL server error log size is too big to handle

    I am working with a large database on windows sql server 2008 R2 such that it has to run continuously 24x7 because of that it is not possible
    to restart the server time to time. It is kind of monitoring system for big machines. Because of this SQL server error logs are growing too big even some times up to 60-70 GB at a limited sized hard drive. I can't delete them time to time manually. Can someone
    please suggest a way using which I can stop creation of such error logs or recycle them after sometime. Most of the errors are of this kind --
    Setting database option RECOVERY to simple for database db_name
    P.S.- I have read limiting error logs to 6 etc. But that didn't help. It will be best if you could suggest some method to disable these logs.

    Hi Mohit11,
    According to your description, your SQL Server error logs are growing too big to handle at a limited sized hard drive, and you want to know how to stop the generation of such error logs or recycle them after sometime automatically without restarting the
    SQL Server, right?
    As others mentioned above, we may not be able to disable SQL server error log generation. However we can recycle the error logs automatically by running the
    sp_cycle_errorlog on a fixed schedule (i.e. every two weeks) using SQL agent jobs so that the error logs will be recycled
    automatically without restarting SQL Server.
    And it is also very important for us to keep the error log files more readable. So we can increase the number of error logs a little more and run the sp_cycle_errorlog more frequently (i.e. daily), then each file will in a smaller size to be more readable
    and we can recycle the log files automatically.
    In addition, in order to avoid the size of all the log files growing into a too big size unexpected (sometime it may happen), we can run the following query in SQL Agent job to automatically delete all the old log files when the size of log files is larger
    than some value we want to keep (i.e. 30GB):
    --create a tample table to gather the information of error log files
    CREATE TABLE #ErrorLog
    Archieve INT,
    Dt DATETIME,
    FileSize INT
    GO
    INSERT INTO #ErrorLog
    EXEC xp_enumerrorlogs
    GO
    --delete all the old log files if the size of all the log files is larger than 30GB
    DECLARE @i int = 1;
    DECLARE @Log_number int;
    DECLARE @Log_Max_Size int = 30*1024; --here is the max size (M) of all the error log files we want to keep, change the value according to your requirement
    DECLARE @SQLSTR VARCHAR(1000);
    SET @Log_number = (SELECT COUNT(*) FROM #ErrorLog);
    IF (SELECT COUNT(FileSize/1024/1024) FROM #ErrorLog) >= @Log_Max_Size
    BEGIN
    WHILE @i <= @Log_number
    BEGIN
    SET @SQLSTR = 'DEL C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\Log\ERRORLOG.' + CONVERT(VARCHAR,@i);
    EXEC xp_cmdshell @SQLSTR;
    SET @i =@i + 1;
    END
    END
    DROP TABLE #ErrorLog
    For more information about How to manage the SQL Server error log, please refer to the following article:
    http://support.microsoft.com/kb/2199578
    If you have any question, please feel free to let me know.
    Regards,
    Jerry Li

  • Tablespace temp grows too much

    Hi gurus,
    i´m using OBIEE 10.1.3.4 . When i´doing a select over a materialized view, the tablespace temp grows too much ( about 15GB).
    The columns of the materialized view are functions.
    The base tables of the Materialized View are big, thousands of MB.
    Is it possible to configure the tablespace temp with OBIEE? and via SQL-PLUS?
    Best Regards.
    Roberto.

    you can do it with Oracle Enterprise Manager, that is much easier way. If you don't have access to OEM and has privileges to alter table space. the command is something like
    alter tablespace ts_sth add datafile \etc\temp.dbf' size 4M autoextend on;

  • Tablespace temp grows too much when using OBIEE

    Hi gurus,
    i´m using OBIEE 10.1.3.4 . When i´doing a select over a materialized view, the tablespace temp grows too much ( about 15GB).
    The columns of the materialized view are functions.
    The base tables of the Materialized View are big, thousands of MB.
    Is it possible to configure the tablespace temp with OBIEE? and via SQL-PLUS?
    Best Regards.
    Roberto.

    you can do it with Oracle Enterprise Manager, that is much easier way. If you don't have access to OEM and has privileges to alter table space. the command is something like
    alter tablespace ts_sth add datafile \etc\temp.dbf' size 4M autoextend on;

  • TEMP too big

    Hey all,
    My temp tablespace has grown too big (19Gb after I ran a particularly bad cart. join). I can't figure out how to get it cleaned up and I'd like my disk back. I've modified the max through OEM, but now it just shows that I'm using more than the max. Tried shutting down and restarting the service and the machine with no luck. How can I get SMON to do his job?
    Win2K Pro
    Oracle Database 10g Release 10.1.0.2.0
    As always, thanks,
    Pete

    There's no automatic shrinking of temporary tablespace, Oracle says, this is a feature, not a bug. The workaround is : Create a new temporary tablespace with smaller size:
    SQL> create temporary tablespace TEMP1 tempfile 'c:\temp01.dbf' size 100M extent management
    local uniform size 128K;
    -- Set new tablespace as default temporary tablespace for all users in database.
    SQL> alter user <username> temporary tablespace TEMP1;
    If you have a large number of users, the following SQL can be used to generate the code to change them all.
    SQL> select 'alter user '||username||' temporary tablespace TEMP1;'
    from dba_users;
    -- Drop the old tablespace.
    SQL> drop tablespace temp including contents.

  • TEMP Tablespace too small

    Hi all,
    We have an Oracle 10.2.0.4 Reporting database, of which every night al lot of data is refreshed from production databases.
    For this refresh this database uses complex Materialized View definitions.
    We recently keep running out of TEMP tablespace during the refresh of these MV's. The TEMP tablespace has lately been increased several times ( in total from 15Gb to 25Gb the last months).
    The largets MV is just 3Gb's big. Especially the one that ran out of TEMP tablespace last night is only 1Gb big.
    The error message:
    ORA-12008: error in materialized view refresh path
    ORA-12801: error signaled in parallel query server P002
    ORA-01652: unable to extend temp segment by 64 in tablespace TEMP
    Can anyone tell me what could cause this behaviour ??
    Some specs:
    Oracle 10.2.0.4
    Platform: AIX 5.3 TL06
    sga_target = 3504M
    parallel_max_servers=8
    temp_tablespace_size=25600Mb
    Thanks in advance

    They are COMPLETE refreshes.
    Statement of the view:
    SELECT /*+ NO_USE_HASH_AGGREGATION */
    mon.mon_description AS mon_mon_descr, mon.mon_code AS mon_mon_code,
    mon.yer_code AS mon_yer_code, cus.iet_descr AS cus_iet_descr,
    prd.igp_nr AS prd_igp_nr, prd.igp_descr_german AS prd_igp_descr_ger,
    prd.igp_descr_dutch AS prd_igp_descr_dut,
    prd.igp_descr_english AS prd_igp_descr_eng,
    prd.igp_descr_czech AS prd_igp_descr_ces,
    prd.igp_descr_russian AS prd_igp_descr_rus, prd.pgp_nr AS prd_pgp_nr,
    prd.pgp_descr_german AS prd_pgp_descr_ger,
    prd.pgp_descr_dutch AS prd_pgp_descr_dut,
    prd.pgp_descr_english AS prd_pgp_descr_eng,
    prd.pgp_descr_czech AS prd_pgp_descr_ces,
    prd.pgp_descr_russian AS prd_pgp_descr_rus, prd.dvs_nr AS prd_dvs_nr,
    prd.dvs_descr_german AS prd_dvs_descr_ger,
    prd.dvs_descr_dutch AS prd_dvs_descr_dut,
    prd.dvs_descr_english AS prd_dvs_descr_eng,
    prd.dvs_descr_czech AS prd_dvs_descr_ces,
    prd.dvs_descr_russian AS prd_dvs_descr_rus,
    cus.pce_descr AS cus_pce_descr, cus.smk_descr AS cus_smk_descr,
    cus.org_descr AS cus_org_descr, cus.dpm_descr AS cus_dpm_descr,
    cus.cmp_descr AS cus_cmp_descr, cus.cgp_descr AS cus_cgp_descr,
    cus.cus_nr AS cus_cus_nr, cus.cus_descr AS cus_cus_descr,
    cus.cus_billto_nr AS cus_billto_nr,
    SUM (fin.invoice_discount_eur) AS invoice_discount_eur,
    SUM (fin.invoice_discount_gbp) AS invoice_discount_gbp,
    SUM (fin.invoice_line_discount_eur) AS invoice_line_discount_eur,
    SUM (fin.invoice_line_discount_gbp) AS invoice_line_discount_gbp,
    SUM (fin.turnover_cr_eur) AS turnover_cr_eur,
    SUM (fin.turnover_cr_gbp) AS turnover_cr_gbp,
    SUM (fin.turnover_deb_eur) AS turnover_deb_eur,
    SUM (fin.turnover_deb_gbp) AS turnover_deb_gbp,
    SUM (fin.turnover_eur) AS turnover_eur,
    SUM (fin.turnover_gbp) AS turnover_gbp,
    SUM (fin.count_credit_slips) AS count_credit_slips,
    cus.srp_nr AS cus_srp_nr, cus.srp_descr AS cus_srp_descr,
    COUNT (*) AS total_records,
    COUNT (fin.count_credit_slips) AS num_count_credit_slips,
    cus.cus_branch AS cus_branch_nr, cus.cus_district AS cus_district_nr,
    SUM (fin.profit_eur) AS profit_eur,
    SUM (fin.profit_gbp) AS profit_gbp,
    SUM (fin.cost_price_eur) AS costs_eur,
    SUM (fin.cost_price_gbp) AS costs_gbp,
    SUM (fin.invoice_discount_chf) AS invoice_discount_chf,
    SUM (fin.invoice_line_discount_chf) AS invoice_line_discount_chf,
    SUM (fin.turnover_cr_chf) AS turnover_cr_chf,
    SUM (fin.turnover_deb_chf) AS turnover_deb_chf,
    SUM (fin.turnover_chf) AS turnover_chf,
    SUM (fin.profit_chf) AS profit_chf,
    SUM (fin.cost_price_chf) AS costs_chf,
    SUM (fin.invoice_discount_czk) AS invoice_discount_czk,
    SUM (fin.invoice_line_discount_czk) AS invoice_line_discount_czk,
    SUM (fin.turnover_cr_czk) AS turnover_cr_czk,
    SUM (fin.turnover_deb_czk) AS turnover_deb_czk,
    SUM (fin.turnover_czk) AS turnover_czk,
    SUM (fin.profit_czk) AS profit_czk,
    SUM (fin.cost_price_czk) AS costs_czk,
    SUM (fin.invoice_discount_rub) AS invoice_discount_rub,
    SUM (fin.invoice_line_discount_rub) AS invoice_line_discount_rub,
    SUM (fin.turnover_cr_rub) AS turnover_cr_rub,
    SUM (fin.turnover_deb_rub) AS turnover_deb_rub,
    SUM (fin.turnover_rub) AS turnover_rub,
    SUM (fin.profit_rub) AS profit_rub,
    SUM (fin.cost_price_rub) AS costs_rub,
    COUNT (fin.invoice_discount_eur) AS cnt_invoice_discount_eur,
    COUNT (fin.invoice_discount_gbp) AS cnt_invoice_discount_gbp,
    COUNT
    (fin.invoice_line_discount_eur)
    AS cnt_invoice_line_discount_eur,
    COUNT
    (fin.invoice_line_discount_gbp)
    AS cnt_invoice_line_discount_gbp,
    COUNT (fin.turnover_cr_eur) AS cnt_turnover_cr_eur,
    COUNT (fin.turnover_cr_gbp) AS cnt_turnover_cr_gbp,
    COUNT (fin.turnover_deb_eur) AS cnt_turnover_deb_eur,
    COUNT (fin.turnover_deb_gbp) AS cnt_turnover_deb_gbp,
    COUNT (fin.turnover_eur) AS cnt_turnover_eur,
    COUNT (fin.turnover_gbp) AS cnt_turnover_gbp,
    COUNT (fin.profit_eur) AS cnt_profit_eur,
    COUNT (fin.profit_gbp) AS cnt_profit_gbp,
    COUNT (fin.cost_price_eur) AS cnt_costs_eur,
    COUNT (fin.cost_price_gbp) AS cnt_costs_gbp,
    COUNT (fin.invoice_discount_chf) AS cnt_invoice_discount_chf,
    COUNT
    (fin.invoice_line_discount_chf)
    AS cnt_invoice_line_discount_chf,
    COUNT (fin.turnover_cr_chf) AS cnt_turnover_cr_chf,
    COUNT (fin.turnover_deb_chf) AS cnt_turnover_deb_chf,
    COUNT (fin.turnover_chf) AS cnt_turnover_chf,
    COUNT (fin.profit_chf) AS cnt_profit_chf,
    COUNT (fin.cost_price_chf) AS cnt_costs_chf,
    COUNT (fin.invoice_discount_czk) AS cnt_invoice_discount_czk,
    COUNT
    (fin.invoice_line_discount_czk)
    AS cnt_invoice_line_discount_czk,
    COUNT (fin.turnover_cr_czk) AS cnt_turnover_cr_czk,
    COUNT (fin.turnover_deb_czk) AS cnt_turnover_deb_czk,
    COUNT (fin.turnover_czk) AS cnt_turnover_czk,
    COUNT (fin.profit_czk) AS cnt_profit_czk,
    COUNT (fin.cost_price_czk) AS cnt_costs_czk,
    COUNT (fin.invoice_discount_rub) AS cnt_invoice_discount_rub,
    COUNT
    (fin.invoice_line_discount_rub)
    AS cnt_invoice_line_discount_rub,
    COUNT (fin.turnover_cr_rub) AS cnt_turnover_cr_rub,
    COUNT (fin.turnover_deb_rub) AS cnt_turnover_deb_rub,
    COUNT (fin.turnover_rub) AS cnt_turnover_rub,
    COUNT (fin.profit_rub) AS cnt_profit_rub,
    COUNT (fin.cost_price_rub) AS cnt_costs_rub
    FROM /* dwh_internal_external_dim iet */
    dwh_customers_dim cus /* department */
    , dwh_products_dim prd /* itemgroup */
    , dwh_months_dim mon
    , dwh_financial_fct fin
    WHERE fin.mon_code = mon.mon_code
    AND fin.prd_id = prd.prd_id
    AND fin.cus_cus_id = cus.cus_id
    GROUP BY mon.mon_description,
    mon.mon_code,
    mon.yer_code,
    cus.iet_descr,
    prd.igp_nr,
    prd.igp_descr_german,
    prd.igp_descr_dutch,
    prd.igp_descr_english,
    prd.igp_descr_czech,
    prd.igp_descr_russian,
    prd.pgp_nr,
    prd.pgp_descr_german,
    prd.pgp_descr_dutch,
    prd.pgp_descr_english,
    prd.pgp_descr_czech,
    prd.pgp_descr_russian,
    prd.dvs_nr,
    prd.dvs_descr_german,
    prd.dvs_descr_dutch,
    prd.dvs_descr_english,
    prd.dvs_descr_czech,
    prd.dvs_descr_russian,
    cus.pce_descr,
    cus.smk_descr,
    cus.org_descr,
    cus.dpm_descr,
    cus.cmp_descr,
    cus.cgp_descr,
    cus.cus_nr,
    cus.cus_descr,
    cus.cus_billto_nr,
    cus.srp_nr,
    cus.srp_descr,
    cus.cus_branch,
    cus.cus_district;
    Explain plan:
    Plan
    SELECT STATEMENT CHOOSE Cost: 278,496 Bytes: 13,752,541,260 Cardinality: 18,864,940
    25 PX COORDINATOR
    24 PX SEND QC (RANDOM) PARALLEL_TO_SERIAL SYS.:TQ10005 :Q1005 Cost: 278,496 Bytes: 13,752,541,260 Cardinality: 18,864,940
    23 SORT GROUP BY PARALLEL_COMBINED_WITH_PARENT :Q1005 Cost: 278,496 Bytes: 13,752,541,260 Cardinality: 18,864,940
    22 PX RECEIVE PARALLEL_COMBINED_WITH_PARENT :Q1005 Cost: 278,496 Bytes: 13,752,541,260 Cardinality: 18,864,940
    21 PX SEND HASH PARALLEL_TO_PARALLEL SYS.:TQ10004 :Q1004 Cost: 278,496 Bytes: 13,752,541,260 Cardinality: 18,864,940
         20 SORT GROUP BY PARALLEL_COMBINED_WITH_PARENT :Q1004 Cost: 278,496 Bytes: 13,752,541,260 Cardinality: 18,864,940
         19 HASH JOIN PARALLEL_COMBINED_WITH_PARENT :Q1004 Cost: 26,390 Bytes: 13,752,541,260 Cardinality: 18,864,940
         4 PX RECEIVE PARALLEL_COMBINED_WITH_PARENT :Q1004 Cost: 55 Bytes: 11,394,614 Cardinality: 70,774
         3 PX SEND BROADCAST PARALLEL_TO_PARALLEL SYS.:TQ10000 :Q1000 Cost: 55 Bytes: 11,394,614 Cardinality: 70,774
         2 PX BLOCK ITERATOR PARALLEL_COMBINED_WITH_CHILD :Q1000 Cost: 55 Bytes: 11,394,614 Cardinality: 70,774
         1 TABLE ACCESS FULL TABLE PARALLEL_COMBINED_WITH_PARENT MIS_RUN.DWH_CUSTOMERS_DIM :Q1000 Cost: 55 Bytes: 11,394,614 Cardinality: 70,774
         18 HASH JOIN PARALLEL_COMBINED_WITH_PARENT :Q1004 Cost: 26,300 Bytes: 10,715,285,920 Cardinality: 18,864,940
         8 PX RECEIVE PARALLEL_COMBINED_WITH_PARENT :Q1004 Cost: 2 Bytes: 2,052 Cardinality: 108
         7 PX SEND BROADCAST PARALLEL_TO_PARALLEL SYS.:TQ10001 :Q1001 Cost: 2 Bytes: 2,052 Cardinality: 108
         6 PX BLOCK ITERATOR PARALLEL_COMBINED_WITH_CHILD :Q1001 Cost: 2 Bytes: 2,052 Cardinality: 108
              5 TABLE ACCESS FULL TABLE PARALLEL_COMBINED_WITH_PARENT MIS_RUN.DWH_MONTHS_DIM :Q1001 Cost: 2 Bytes: 2,052 Cardinality: 108
         17 HASH JOIN PARALLEL_COMBINED_WITH_PARENT :Q1004 Cost: 26,264 Bytes: 10,356,852,060 Cardinality: 18,864,940
         12 PX RECEIVE PARALLEL_COMBINED_WITH_PARENT :Q1004 Cost: 305 Bytes: 178,954,440 Cardinality: 426,082
         11 PX SEND HASH PARALLEL_TO_PARALLEL SYS.:TQ10002 :Q1002 Cost: 305 Bytes: 178,954,440 Cardinality: 426,082
              10 PX BLOCK ITERATOR PARALLEL_COMBINED_WITH_CHILD :Q1002 Cost: 305 Bytes: 178,954,440 Cardinality: 426,082
              9 TABLE ACCESS FULL TABLE PARALLEL_COMBINED_WITH_PARENT MIS_RUN.DWH_PRODUCTS_DIM :Q1002 Cost: 305 Bytes: 178,954,440 Cardinality: 426,082
         16 PX RECEIVE PARALLEL_COMBINED_WITH_PARENT :Q1004 Cost: 11,396 Bytes: 2,433,577,260 Cardinality: 18,864,940
         15 PX SEND HASH PARALLEL_TO_PARALLEL SYS.:TQ10003 :Q1003 Cost: 11,396 Bytes: 2,433,577,260 Cardinality: 18,864,940
         14 PX BLOCK ITERATOR PARALLEL_COMBINED_WITH_CHILD :Q1003 Cost: 11,396 Bytes: 2,433,577,260 Cardinality: 18,864,940
              13 TABLE ACCESS FULL TABLE PARALLEL_COMBINED_WITH_PARENT MIS_RUN.DWH_FINANCIAL_FCT :Q1003 Cost: 11,396 Bytes: 2,433,577,260 Cardinality: 18,864,940
    Thanks again

  • Maximum Temp tablespace size you've seen

    DB version: 10.2.0.4
    Our DB caters a retail application . Total DB Size of 3TB. Its is a bit of mix of both OLTP and Batch processing environment.
    Our temp tablespace has 1 file and we had set the tempfile as AUTOEXTEND. Somehow its size has reached 25GB now !
    We don't actually need this. Do we?
    For a fairly busy DB of around 3TB size, what is the maximum temp tablespace size you've ever seen?
    What is the maximum temp tablespace size you've ever seen for Big DB like Telecom, Banking?

    The point about temp space is that your requirements are dynamic - the actively used area shrinks and grows.
    Comparing apples with oranges, tempfile sizes on system where I am currently here amount to 50 GB but to be honest that's mainly due to a not insignificant number of pretty poor queries, run concurrently, with multipass operations, etc.
    Kellyn Pedersen had an example of a process using 720GB here:
    http://dbakevlar.com/?p=43
    Whilst 25GB may not be earth shattering, a "large" temp area may perhaps be an indicator that you want to review some of your application code.
    (What is "large"? "unusual" compared to what is "normal" for your system may be a better metric)
    If you're using automatic pga memory management, then there's a limit to what each session can get, it may be that automatic work areas are not suitable for some of your code and some manual sizing is required to prevent operations spilling unnecessarily.
    Also, inaccurate CBO estimates on your queries can lead to inaccurately sized work areas that then spill into temp.
    There was a reminder of this in one of Randolf Geist's articles on hash aggregation:
    http://oracle-randolf.blogspot.com/2011/01/hash-aggregation.html

Maybe you are looking for

  • Can't get Target Disk Mode to work with host computer

    Here's the problem. My Powerbook G4 went down a week ago (it's 7 years old) and I suspect the problem is either the hard drive or the portion of the logic board controlling the drive. I also have a Power Mac G4 400 that's running OS 10.4 Tiger. I've

  • Unable to see form previews in BPE

    I am unable to see preview of opend forms in the business process editor.I get the error message 404 file not found. Even if i copy paste the URL in the browser i am unable to see the form please help

  • HDMI to VDI

    Hi I have the A700, if I were to plug in an HDMI to VDI cable on the HDMI output and connect it to a second monitor, would I be able to have both monitors available for viewing, or can I only view one at a time? http://www.computercablestore.com/5_Me

  • Append row in end of table?

    Hi,      I have an ALV table with default "Append row" "Delete Row" buttons. When i give append row initially, then a new row is added to the end of the table. But when i give field sorting (Ascending order), and then go for Append row, a new row whi

  • Downloaded new Ringtone and cant seem to find it on iphone under sounds

    Downloaded, thought it would go directly into category with other types of ring sounds, cant seem to find it. Help