Unable to extend rollback segment 0
I'm migrating a 7.3.4 database to 8.0.5 using MIG80 and i get messages:
ora-01562 Unable to extend rollback segment 0
ora-01528 max # extents <121> reached for rollback segment system
My tablespace system's original size is 120M, now I have it grown to 400M, also have my rbs tablespace grown to 200M, I'm using MULTIPLIER=30, i've migrated 2 databases same sized but this time does'n work.
Can you help me?
I4m kind of hurry, i have to migrate 7 databases by august 25.
Thanks
Dear friend
Create rollback segment with large
in size.
sql> set transaction use rollback segment 'Name of the roll'
suresh
null
Similar Messages
-
ORA-1650: unable to extend rollback segment
Hi,
We have 20 RBS's and in our production instance we got very frequent alerts related to ORA-1650: unable to extend rollback segment continuously. When I looked for select STATUS from v$rollstat; I could see most of them are with FULL status. after couple of hours they disappeared and status became online.
How to avoid these type of alerts?
REgardsWhat version of Oracle?
If you are 9ir2 or later, you should be going to automatic undo management. Though it won't help your 'we cannot add space' restriction. That's not an Oracle problem, that's a corporate issue.
This problem may be caused by poor transaction design with too many processing doing too infrequent commits. That's not an Oracle problem either, that's a corporate/development issue.
So...you don't have an Oracle problem.
You can't stop the 1650s from occurring if you are unwilling to add space or address application issues. However, you can set up an email filter so that any emails containing ORA-01650 in the header or body get automatically sent to the trash.
<sarcasm>
If you can't solve a problem, then just ignore it!
</sarcasm> -
Unable to Extend Rollback Segment
Hi,
This was the error when I tried to create a table with large amount of data using
Create Table As Select * From TableName
Can I handle this error From Pl-Sql
Since the table is created dynamically
through Pl-Sql.
Can I avoid this error by setting following
parameters in the file init.ora.
Transactions
TransactionsPerRollbackSegment
Regards
Mrinal
nullDear friend
Create rollback segment with large
in size.
sql> set transaction use rollback segment 'Name of the roll'
suresh
null -
How to extend rollback segment
Hi,
for a few days I've been getting the following messages:
ORA-01562: failed to extend rollback segment number 3
ORA-01650: unable to extend rollback segment RBS2 by 512 in tablespace RBS
after running a package which has always had no problems and where it's also been added a COMMIT after the insert statements inside the package.
DBAs have tried to increase the rollback segment but the problem is always the same.
Have you got some advice?
Thanks!By adding a datafile in RBS tablespace.
-
Failed to extend Rollback Segment
Version of the database is
Oracle8i Enterprise Edition Release 8.1.7.0.0 - Production
I have a rollback tablespace that is 99%used and wen I am tryng to use DML statements to the database it is throwing the following error.
ORA-01562:FAILED TO EXTEND ROLLBACK SEGMENT 2
ORA-01650:UNABLE TO EXTEND ROLLBACK SEGMENT RBS01 BY 128 IN TABLESPACE
R
May I know how do I proceed now? Do I have to extend the tablespace or add a new datafile to the tablespace?PK wrote:
Version of the database is
Oracle8i Enterprise Edition Release 8.1.7.0.0 - Production
I have a rollback tablespace that is 99%used and wen I am tryng to use DML statements to the database it is throwing the following error.
ORA-01562:FAILED TO EXTEND ROLLBACK SEGMENT 2
ORA-01650:UNABLE TO EXTEND ROLLBACK SEGMENT RBS01 BY 128 IN TABLESPACE
R
May I know how do I proceed now? Do I have to extend the tablespace or add a new datafile to the tablespace?
01562, 00000, "failed to extend rollback segment number %s"
// *Cause: Failure occurred when trying to extend rollback segment
// *Action: This is normally followed by another error message that caused
// the failure. You may take the rollback segment offline to perform
// maintainence. Use the alter rollback segment offline command
// to take the rollback segment offline.
bcm@bcm-laptop:~$ oerr ora 1650
01650, 00000, "unable to extend rollback segment %s by %s in tablespace %s"
// *Cause: Failed to allocate an extent of the required number of blocks for
// a rollback segment in the tablespace.
// *Action: Use ALTER TABLESPACE ADD DATAFILE statement to add one or more
// files to the tablespace indicated. -
DAL Exception: ORA-01562: failed to extend rollback segment number 4
Hi,
in our application log, we got sometimes an error ORA-01562: failed to extend rollback segment number 4 and the application hangs and some transactions are blocked. checking the aler database file, we don't found this error but it's appearing often in our system.
would you lease advise what to do to avaoid this error, or is there a script to find oracle SQl where using too much rollback segment.
My configuration is : Oracle 10g r2 in linux SUSE.
thank you
Lucienot.Hi,
Please refer MOS tech note *ORA-1562 and ORA-1650 Unable to Extend Rollback Segment [ID 1066542.6]*
thanks,
X A H E E R -
ORA-01652: unable to extend temp segment by 128 in tablespace TEMP2
Dear all,
received this error when generate a report.
check the TEMP1 and TEMP2 they all have lot of spaces.
check the env $APPLLCSP return empty.
Please advise how to correct this error.
Regards,
Payables: Version : 12.0.0
APXSSIMP module: Supplier Sites Open Interface Import
APPLLCSP Environment Variable set to :
Current NLS_LANG and NLS_NUMERIC_CHARACTERS Environment Variables are :
American_America.UTF8
Enter Password:
REP-0069: Internal error
REP-57054: In-process job terminated:Terminated with error:
REP-300: MSG-00001: After SRWINIT
MSG-00002: After Get_Company_Name
MSG-00003: After Get_NLS_Strings
MSG-00004: After Importing Suppliers
MSG-00005: After Get_Header_Information
ORA-01652: unable to extend temp segment by 128 in tablespace TEMP2
==> SELECT assi.org_id C_Rejected_Org_Id,
MSG-00020: After SRWEXIT
Report Builder: Release 10.1.2.0.2 - Production on Mon May 11 09:55:36 2009>
check the TEMP1 and TEMP2 they all have lot of spaces.
>
How much is "lot" ? :-) How did you determine this "lot" ?
Pl see MOS Doc 1025288.6 (How to Diagnose and Resolve UNABLE TO EXTEND Errors)
HTH
Srini -
Unable to extend TEMP segment even after adding fresh temp files
Hi All,
I have a huge table with rows nearly 2 million. When this table is moved to another tablespace, the command failed giving the following error:
ORA-01652: unable to extend temp segment by 128 in tablespace XYZ
To overcome this error, an additional temp file was added with huge size. Unfortunately, the same error appeared again when the table was tried to move to another tablespace. I wonder if the new temp file was not recognized by database, so tried to see how many files belong to temporary tablespace, but the query listed the newly added temp file also.
What could be the possible reason for this error? Suggestions or clues are most welcome.
Thanks,
...The temp segment is for the table that is being moved.
Oracle creates a temporary segment when doing a move. If the target tablespace has enough space, the move succeeds and the temp segment gets converted to a Table segment. Else, if the move fails because of lack of space (the temp segment itself unable to grow), then the temp segment is dropped on failure.
Thus, in a
alter table ABC move tablespace MY_TBS;or
the target tablespace MY_TBS should have enough space for ABC. While Oracle is building the copy of ABC in MY_TBS, it is being built as a temporary segment. If the copy succeeds, the temporary segment is renamed as a Table segment 'ABC' and the original table segment 'ABC' is dropped.
This behaviour also happens when you do an ALTER TABLE .. MOVE ; into the same tablespace that it is existing in. The new copy of the table is a temporary sgement till the copy succeeds. -
Unable to extend temp segment by 128 in tablespace PSAPTEMP
Hi everybody!
While processing a UNICODE coversion with SAPINST on my SAP NW2004s system (AIX 5,2 - Oracle 10.2 - BW 7.0) into my.SAPDFACT_1.log file the following errors occured:
DbSl Trace: ORA-1403 when accessing table SAPUSER
(DB) INFO: connected to DB
(DB) INFO: DbSlControl(DBSL_CMD_NLS_CHARACTERSET_GET): UTF8
(GSI) INFO: dbname = "HBQ20080503070541 "
(GSI) INFO: vname = "ORACLE "
(GSI) INFO: hostname = "si088ss1 "
(GSI) INFO: sysname = "AIX"
(GSI) INFO: nodename = "si088ss1"
(GSI) INFO: release = "2"
(GSI) INFO: version = "5"
(GSI) INFO: machine = "0031832B4C00"
(DB) INFO: /BIC/FZHPY_LIM created #20080503200234
(IMP) INFO: import of /BIC/FZHPY_LIM completed (133182692 rows) #20080503212420
DbSl Trace: Error 1652 in exec_immediate() from oci_execute_stmt(), orpc=0
DbSl Trace: ORA-1652 occurred when executing SQL stmt (parse error offset=42)
(DB) ERROR: DDL statement failed
(CREATE UNIQUE INDEX "/BIC/FZHPY_LIM~0" ON "/BIC/FZHPY_LIM" ( "KEY_ZHPY_LIMP", "KEY_ZHPY_LIMT", "KEY_ZHPY_LIMU", "KEY_ZHPY_LIM2", "KEY_ZHPY_LIM3", "KEY_ZHPY_LIM4", "KEY_ZH
PY_LIM5", "KEY_ZHPY_LIM6", "KEY_ZHPY_LIM7" ) TABLESPACE PSAPSR3 STORAGE (INITIAL 65536 NEXT 0000002560K MINEXTENTS 0000000001 MAXEXTENTS 2147483645 PCTINCREASE 0 ) NOLOGGING COMPUTE STATISTICS )
DbSlExecute: rc = 99
(SQL error 1652)
error message returned by DbSl:
ORA-01652: unable to extend temp segment by 128 in tablespace PSAPTEMP
(DB) INFO: disconnected from DB
Anybody can help me?
Thanks a lot!Hi Stefan!
desc SAPSR3."/BIC/FZHPY_LIM";
Name Null? Type
KEY_ZHPY_LIMP NOT NULL NUMBER(10)
KEY_ZHPY_LIMT NOT NULL NUMBER(10)
KEY_ZHPY_LIMU NOT NULL NUMBER(10)
KEY_ZHPY_LIM2 NOT NULL NUMBER(10)
KEY_ZHPY_LIM3 NOT NULL NUMBER(10)
KEY_ZHPY_LIM4 NOT NULL NUMBER(10)
KEY_ZHPY_LIM5 NOT NULL NUMBER(10)
KEY_ZHPY_LIM6 NOT NULL NUMBER(10)
KEY_ZHPY_LIM7 NOT NULL NUMBER(10)
/BIC/ZHCONTING NOT NULL NUMBER(17,2)
/BIC/ZHD_IMP NOT NULL NUMBER(17,2)
/BIC/ZHPERC2 NOT NULL NUMBER(10)
SELECT AVG_ROW_LEN FROM ALL_TABLES WHERE TABLE_NAME = '/BIC/FZHPY_LIM';
AVG_ROW_LEN
SELECT BYTES, BLOCKS FROM DBA_SEGMENTS WHERE SEGMENT_NAME = '/BIC/FZHPY_LIM';
BYTES BLOCKS
7180648448 876544
SELECT FILE_NAME, TABLESPACE_NAME, BYTES, BLOCKS, AUTOEXTENSIBLE, MAXBYTES, MAXBLOCKS FROM DBA_TEMP_FILES;
FILE_NAME
TABLESPACE_NAME BYTES BLOCKS AUT MAXBYTES MAXBLOCKS
/oracle/HBQ/sapdata1/temp_1/temp.data1
PSAPTEMP 1048576000 128000 YES 1.0486E+10 1280000
/oracle/HBQ/sapdata1/temp_1/temp2.data1
PSAPTEMP 298844160 36480 YES 3.4359E+10 4194176
Thanks. -
Hi All,
I received the following error;
ORA-01652: unable to extend temp segment by 128 in tablespace TEMP2
Then I added the datafile in temp2 tablespace.
But still it giving the same error;
Syntax of Create tablespace is
Create temporary tablespace temp2
Datafile \temp_01.dbf size 500m;
Table contains 100000 records;
Please help me.
Thanks and regards,
Prathamesh.Please check the allocation and deallocation of space in a temporary tablespace sort segment using the V$SORT_SEGMENT view. The V$TEMPSEG_USAGE view identifies the current sort users in those segments.
Also, check settings of TEMP tablespace. May be it's trying to create a huge extent as NEXT (larger than available space), which is not required. In that case reduce NEXT EXTENT for this. -
Add Unique Constraint - Unable to extend temp segment
I'm getting the error "ORA-01652: unable to extend temp segment by 1024 in tablespace ...". I'm a developer, and our DBA is on vacation. I'm trying to understand what's happening, so I monitor V$SORT_SEGMENT while the constraint is being created. Here is what that view looks like immediately before and after the exception is thrown:
10:43:07 < ... > select * from v$sort_segment;
TABLESPACE_NAME SEGMENT_FILE SEGMENT_BLOCK EXTENT_SIZE CURRENT_USERS TOTAL_EXTENTS TOTAL_BLOCKS USED_EXTENTS USED_BLOCKS FREE_EXTENTS FREE_BLOCKS ADDED_EXTENTS EXTENT_HITS FREED_EXTENTS
FREE_REQUESTS MAX_SIZE MAX_BLOCKS MAX_USED_SIZE MAX_USED_BLOCKS MAX_SORT_SIZE MAX_SORT_BLOCKS RELATIVE_FNO
TEMP 0 0 128 1 460 58880 460 58880 0 0 460 505 2809
1 2809 359552 460 58880 460 58880 0
Elapsed: 00:00:00.04
10:43:13 < ... > select * from v$sort_segment;
TABLESPACE_NAME SEGMENT_FILE SEGMENT_BLOCK EXTENT_SIZE CURRENT_USERS TOTAL_EXTENTS TOTAL_BLOCKS USED_EXTENTS USED_BLOCKS FREE_EXTENTS FREE_BLOCKS ADDED_EXTENTS EXTENT_HITS FREED_EXTENTS
FREE_REQUESTS MAX_SIZE MAX_BLOCKS MAX_USED_SIZE MAX_USED_BLOCKS MAX_SORT_SIZE MAX_SORT_BLOCKS RELATIVE_FNO
TEMP 0 0 128 0 460 58880 0 0 460 58880 460 505 2809
1 2809 359552 460 58880 460 58880 0
Elapsed: 00:00:00.02My DBA had previously instructed me to issue this command to try to avoid this error:
alter database tempfile '...' resize 12g;I do that, but I still only show 460 free segments. Can someone point me to some documentation on how to make the Free Extents be larger than 460?
Here's my client info:
SQL*Plus: Release 11.2.0.3.0 Production on Tue Nov 6 10:40:39 2012
Copyright (c) 1982, 2011, Oracle. All rights reserved.Here's my server info:
Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing optionsGiven that you appear to be able to add/increase temp files, you are also likely to be able to see the dba_* views. As a first shot, try:
select sum(bytes) from dba_free_space
where tablespace_name = <name from the error message>If there appears to be sufficient space (no idea what that would be since I do not know how big your objects are) then try something like:
select file_id, block_id, bytes from dba_free_space
where tablespace_name = <name from the error message>
order by bytes descIf you have large amounts of contiginous free space (i.e. the first few rows have a large value for the bytes column) then ther may be something else going on.
If both queries show relativel small values for the amount of free space, you will need to add another datafile to the tablespace, or increase the size of one of the existing datafile.
To see the datafiles in the tablespace use:
select file_name, bytes from dba_data_files
where tablespace_name = <name from the error message>You can increase the size of a datafile using something similar to the alter database command you have for the tempfiles like:
alter database datafile <a quoted full name from dba_data_files> resize some bigger numberJust make sure that the file system has enough free space for the new size.
John -
ORA-1652: unable to extend temp segment by 128 in tablespace
HI,
i am getting an error in alert log file.....
Thread 1 advanced to log sequence 1758
Current log# 2 seq# 1758 mem# 0: /dev/vx/rdsk/racdg/orcl_raw_log12
Mon Sep 8 12:34:16 2008
ARC1: Evaluating archive log 1 thread 1 sequence 1757
ARC1: Beginning to archive log 1 thread 1 sequence 1757
Creating archive destination LOG_ARCHIVE_DEST_1: '/arch/log/1_1757.dbf'
ARC1: Completed archiving log 1 thread 1 sequence 1757
Mon Sep 8 13:04:26 2008
Completed checkpoint up to RBA [0x6de.2.10], SCN: 0x0000.6c1f757f
Mon Sep 8 13:49:16 2008
ORA-1652: unable to extend temp segment by 128 in tablespace TEMPI don';t want to add datafile
SQL> select bytes,maxbytes,increment_by from dba_temp_files;
BYTES MAXBYTES INCREMENT_BY
6134169600 0 0
SQL> select TABLESPACE_NAME, BYTES_USED, BYTES_FREE from V$TEMP_SPACE_HEADER;
TABLESPACE_NAME BYTES_USED BYTES_FREE
TEMP 6037700608 96468992i have also referred metalink note: 19047.1
Is there any way to avoid this problem without adding any datafile........how to find out which session is using temp tablespace
SQL> select * from v$sort_usage;
USERNAME USER SESSION_ADDR
SESSION_NUM SQLADDR SQLHASH TABLESPACE
CONTENTS SEGTYPE SEGFILE# SEGBLK# EXTENTS BLOCKS SEGRFNO#
DATA3 DATA3 000000044D84F558
25860 00 0 TEMP
TEMPORARY DATA 201 183561 1 128 1pls correct me if the above query is worng to find out the no. of session s using temp tablespace
i think we have already allocated good amt of space to pga_aggregate_target
SQL> show parameter pga
NAME TYPE VALUE
pga_aggregate_target big integer 524288000
SQL>Edited by: user00726 on Sep 8, 2008 2:29 AM -
The Sky is Falling! ORA-01652: unable to extend temp segment by 128
So we currently have a production problem and I'm not so in the know as a lowly java developer and not an Oracle expert.
We keep getting this error(below) when a certain heavy query hits the DB.
Our DBA claims that the tablespace for 'TABLE_SPACE_NAME_HERE' is 20GB of space and that the problem is the query.
The query has been running fine for many many months but all of a sudden is presenting a problem and we have to do something quick.
We tried bouncing the application server but the error came right back when the big select query gets hit.
Any thoughts? Help! : )
java.sql.SQLException: ORA-01652: unable to extend temp segment by 128 in tablespace TABLE_SPACE_NAME_HERE
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:113)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:331)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:288)
at oracle.jdbc.driver.T4C8Oall.receive(T4C8Oall.java:754)
at oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:219)
at oracle.jdbc.driver.T4CPreparedStatement.executeForRows(T4CPreparedStatement.java:972)
at oracle.jdbc.driver.OracleStatement.executeMaybeDescribe(OracleStatement.java:1074)
at oracle.jdbc.driver.T4CPreparedStatement.executeMaybeDescribe(T4CPreparedStatement.java:854)
at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1156)
at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3415)
at oracle.jdbc.driver.OraclePreparedStatement.executeQuery(OraclePreparedStatement.java:3460)
at org.jboss.resource.adapter.jdbc.WrappedPreparedStatement.executeQuery(WrappedPreparedStatement.java:296)LosLobo wrote:
So, the next question... what is our lesson learned in this case?It depends on the root cause.
Our DBA thinks 30GB is an unreasonable size for the tablespace and is fingering the select query that was causing the error to occur. Their solution is move to the query to a view and then reduce the tablespace back to 20GB.
My thoughts are shouldn't the DB be able to handle a query that has been running fine for the last couple years? Also, if we do what is suggested what would prevent another query from coming along and causing the same issue all over again?Has the DBA identified the source of the issue? Did the query plan change? It's possible that something with statistics (or with some configuration change) causes Oracle to believe that two different query plans are roughly equally efficient. One plan might take substantially more TEMP space than another. It's possible that Oracle had been choosing the plan that involved less TEMP space being used and recently changed to preferring the plan that takes more TEMP space. If that's the issue, you may want to force Oracle to use the plan that involves less TEMP usage.
Regardless of your TEMP tablespace size, another query may come along that causes TEMP to run out of space. Or data growth may cause TEMP to run out of space. Or an increase in the number of users may cause TEMP to run out of space. Ideally, the DBAs would be identifying how much TEMP space is used over the course of the day so that if things are growing steadily additional space can be added as necessary. If TEMP space increases dramatically because a query plan changes, however, even the best monitoring is unlikely to be able to predict that level of growth.
Whether 30 GB is unreasonable (or whether 20 GB is unreasonable) will depend heavily on your application. We don't know enough to be able to comment. A TB-sized OLTP database serving millions of customers will have very different TEMP requirements than a multi-TB data warehouse which will have very different TEMP requirements than a small department-level application.
My surmising is we must have just crossed a watermark threshold and the simplest most reasonable solution is to just leave the larger tablespace size.Why do you believe this is the case? It is entirely possible that you need more TEMP because your TEMP usage has been growing slowly over time. It is entirely possible that the query in question has always been using more TEMP space than it really should and that you finally have enough usage to cause the problem to bubble to the surface. It is entirely possible that the query used a reasonable amount of TEMP for the past couple years and suddenly started using far more because of a query plan change. Once you identify the source of the problem, we can figure out the appropriate solution. Without knowing the source of the problem, we're all just guessing.
Justin -
ORA-01652: unable to extend temp segment by 128 in tablespace TEMP
Hi,
I am getting the following error while executing an insert query.
ORA-01652: unable to extend temp segment by 128 in tablespace TEMP.
I have tried increasing the TEMP tbsp size it got resolved temporarily but occurred again after few days.
When the problem occured, following query shows all insert queries in TEMP tablespace and one of them consumes about 5GB and others are about 24MB.
SELECT S.sid || ',' || S.serial# sid_serial, S.username,
T.blocks * TBS.block_size / 1024 / 1024 mb_used, T.tablespace,
T.sqladdr address, Q.hash_value, Q.sql_text
FROM v$sort_usage T, v$session S, v$sqlarea Q, dba_tablespaces TBS
WHERE T.session_addr = S.saddr
AND T.sqladdr = Q.address (+)
AND T.tablespace = TBS.tablespace_name
ORDER BY S.sid;
The insert query is :
INSERT INTO SEOSDATA (ENTRYID,DOMAINNAME,USERNAME,EVENTTYPE,LOGNAME,TIMSTAMP,SOURCE,COMPUTERNAME,EVENTID,EVENTCATEGORY,SEARCHSTRINGS,MSGTEXT) VALUES (ENTRYID_SEQ.NEXTVAL,:1,:2,:3,:4,:5,:6,:7,:8,:9,:10,:11)
It is not expected that an insert query consumes such a huge memory.
Can someone help me in figuring out what the problem is.
What might have gone wrong? Seems like sorting is used, why an insert query uses sorting?
Regards
IshuHi,
Insert statement should not use TEMP tablespace. Please check with following query which user and session id is using TEMP tablespace.
SELECT b.tablespace, b.segfile#, b.segblk#, b.blocks, a.sid, a.serial#,
a.username, a.osuser, a.status
FROM v$session a,v$sort_usage b
WHERE a.saddr = b.session_addr
ORDER BY b.tablespace, b.segfile#, b.segblk#, b.blocks;
Dilipkumar Patel. -
ORA-01652: unable to extend temp segment by 8192 in tablespace CDR_TAB
Dear All,
While create index command
"create index idx_CALLED_NO on dbs(CALLED_NO) nologging"
an error occure
ORA-01652: unable to extend temp segment by 8192 in tablespace CDR_TAB
how to retify it.what is the command to add datafile or tablespace......
Using oracle 9i...
Thanks in advancecreate tablespace or add index, that you can find out at http://tahiti.oracle.com
You should check space on CDR_TAB.
I think you can create new tablespace
http://download.oracle.com/docs/cd/B10501_01/server.920/a96540/statements_74a.htm#SQLRF01403
Create tablespace CDR_IND datafile 'xxx' ...After that create index
create index idx_CALLED_NO on dbs(CALLED_NO) nologging tablespace CDR_IND ;Good Luck;)
Maybe you are looking for
-
Sending email using UTL_SMTP
Dear experts, I am trying to send an email using UTL_SMTP (i switched from UTL_MAIL to UTL_SMTP since i need to send mails with large attachments - BLOB). I am using the demo_mail package given here: http://www.oracle.com/technology/sample_code/tech/
-
This Formula(Function) compiles but does not display any result
Please can anybody help me resolve this issue.The code below is a code for a formula(function) column in oracle report, i have complied this code and it successfully complied but it does not display any result for the column having a stock balance in
-
Iphoto does not use the proper display profile
Hello. I just bought a 20' Apple Cinema display and connected it to my Macbook. I have noticed a very strange behavior of iPhoto and Preview. I will first describe the expected (right behaviour). When I drag an image opened in Adobe LG or Aperture fr
-
Boldface won't "stick" in database document
I'm using a large database document in AppleWorks in which some text is boldfaced. Boldface won't "stick" in those fields now -- if I boldface some text, it returns to lightface as soon as I move out of the field. If I enter a field where the text is
-
JPG files attached to mails - can't open directly
I use webmail applications (not directly 'Mail' from Mac OS) and when image JPG files are attached, and click on them to open them, the computer considers them as 'binary file' and only allows to save to disk - then, on the disk, Mac opens them with