Index space

Hi
1-)
Suppose I delete a value (for example: 2) from table which is indexed.
Does the index space occupied by value 2 ever used again?
or
Supose I have table with values 1 to 500.000.
When I delete all even numbers,Does these space ever used again?
2-)
Does coalece automatically gives space to tablespace?

Does coalesce returns the space to the tablespace?Not with your example!
As rows are deleted from an index, Oracle "logically deletes" the rows, leaving space for subsequent inserts.
That's why you cannot specify the freelist re-link threshold (PCTUSED) for indexes . . .
http://www.dba-oracle.com/art_tpg_auto_space.htm
Hope this helps . . .
Donald K. Burleson
Oracle Press author
Author of "Oracle Tuning: The Definitive Reference"
http://www.rampant-books.com/book_2005_1_awr_proactive_tuning.htm

Similar Messages

10g: How to determine Local Partition Index Space UTILIZATION

I'm trying to determine how much space is actually utilized by different local partition indexes. Some are b-tree and some are bitmap. So far when I query dba_segments and dba_part_indexes I just see space available, not the space utilized.
Does anybody know a way to know the actual space utilized by a local partition index?

Does anybody know a way to know the actual space utilized by a local partition index?SUM(BYTES) from dba_extents
SQL> desc dba_extents
Name                            Null?    Type
OWNER                                  VARCHAR2(30)
SEGMENT_NAME                             VARCHAR2(81)
PARTITION_NAME                         VARCHAR2(30)
SEGMENT_TYPE                             VARCHAR2(18)
TABLESPACE_NAME                        VARCHAR2(30)
EXTENT_ID                             NUMBER
FILE_ID                             NUMBER
BLOCK_ID                             NUMBER
BYTES                                  NUMBER
BLOCKS                              NUMBER
RELATIVE_FNO                             NUMBER

Total space used by indexes for specific schema

Hi all.
Running Oracle 9.2.0.4.
Is there a way I can see how much index space is used for a specific schema? I query index_stats and it returns 0 rows but my stats were updated this morning.
Any input is apreciated.
Thanks

Hi,
Index space and index stats are two different things.
What you are interested to know?
1) How much space is used by index for a particular schema
select sum(bytes)/1024/1024 from dba_segments
where (owner, segment_name) in
(select owner, index_name from dba_indexes where
owner = '<schema you are interested in>')2) Is the stats gathered on index
select index_name, last_analyzed, num_rows from dba_indexes where
owner = <'schema you are interested in >'Regards
Anurag

Coalesce or compress this index? what is the best solution in this case?

BANNER
Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64biI have executed the following query on a specific index that I suspected to be smashed and got the following result
select
    keys_per_leaf, count(*) blocks
from (
      select   sys_op_lbid (154813, 'L', jus.rowid) block_id,
             count (*)                            keys_per_leaf
      from xxx_table jus
       where jus.id is not null
              or jus.dat is not null
      group by sys_op_lbid (154813, 'L', jus.rowid)
group by keys_per_leaf
order by keys_per_leaf;
keys_per_leaf     blocks
1     80
2     1108
3     2816
4     3444
5     3512
6     2891
7     2579
8     2154
9     1943
10     1287
11     1222
12     1011
13     822
14     711
15     544
16     508
17     414
18     455
19     425
20     417
21     338
22     337
23     327
24     288
25     267
26     295
27     281
28     266
29     249
30     255
31     237
32     259
33     257
34     232
35     211
36     209
37     204
38     216
39     189
40     194
41     187
42     200
43     183
44     167
45     186
46     179
47     179
48     179
49     171
50     164
51     174
52     157
53     181
54     192
55     178
56     162
57     155
58     160
59     153
60     151
61     133
62     177
63     156
64     167
65     162
66     171
67     154
68     162
69     163
70     153
71     189
72     166
73     164
74     142
75     177
76     148
77     161
78     164
79     133
80     158
81     176
82     189
83     347
84     369
85     239
86     239
87     224
88     227
89     214
90     190
91     230
92     229
93     377
94     276
95     196
96     218
97     217
98     227
99     230
100     251
101     266
102     298
103     276
104     288
105     638
106     1134
107     1152
229     1
230     1      This is a 5 columns unique key index on (id number, dat date, id2 number, dat2 date type number).
Furthermore, a space analysis of this index using dbms_space.space_usage gives the following picture
Number of blocks with at least 0 to 25% free space            = 0                   -------> total bytes = 0
Number of blocks with at least 25-50% free space              = 75                 -------> total bytes = ,5859375
Number of Blocks with with at least 50 to 75% free space = 0                   -------> Total Bytes = 0
number of blocks with at least 75 to 100% free space        = 0                   -------> total bytes = 0
Number of full blocks with no free space                              = 99848           -------> total bytes = 780,0625
Total blocks ______________________________
99923
Total size MB______________________________
799,384It seems for me that this index needs to be either coalesced or compressed.
Then, what would be the best option in your opinion?
Thanks in advance
Mohamed Houri
Edited by: Mohamed Houri on 12-janv.-2011 1:18

So let me continue my case
I first compressed the index as follows
alter index my_index rebuild compress 2;which immediately presents two new situations
(a) index space
Number of blocks with at least 0 to 25% free space    = 0                -------> total bytes = 0
Number of blocks with at least 25-50% free space      = 40              -------> total bytes =, 3125
Number of Blocks with at least 50 to 75% free space   = 0                -------> total Bytes = 0
Number of blocks with at least 75 to 100% free space = 0                -------> total bytes = 0
Number of full blocks with no free space                = 32361           -------> total bytes = 252, 8203125
Total blocks ______________________________
32401
Total size Mb______________________________
259,208meaning that the compress command freed up 67487 leaf blocks and reduced the size of the index from to 799,384 MB to 259,208 MB.
It also shows a relative nice pictue of number of keys per leaf block (when compared to the previous situation)
(b) on the number of key per leaf block
KEYS_PER_LEAF     BLOCKS
4     1
6     1
13     1
15     1
25     1
62     1
63     1
88     1
97     1
122     1
123     3
124     6
125     4
126     2
289     4489
290     3887
291     3129
292     2273
293     1528
294     913
295     442
296     152
297     50
298     7
299     1      In a second step, I have coalesced the index as follows
alter index my_index coalesce;which produces the new figure
Number of blocks with at least 0 to 25% free space     = 0          -------> total bytes = 0
Number of blocks with at least 25-50% free space      = 298        -------> total bytes = 2,328125
Number of Blocks with at least 50 to 75% free space   = 0           -------> Total Bytes = 0
Number of blocks with at least 75 to 100% free space = 0            -------> total bytes = 0
Number of full blocks with no free space = 32375                    -------> total bytes = 252, 9296875
Total blocks ______________________________
32673
Total size MB______________________________
261,384meaning the the coalesce command has made
(a)     298-40 = 258 new blocks with 25-50% of free space
(b)     32375-32361 = 14 new additional blocks which have been made full
(c)     The size of the index increased by 2,176MB (261,384-259,208)
While the number of key per leaf block keeps in the same situation
KEYS_PER_LEAF     BLOCKS
4     2
5     3
9     1
10     2
12     1
13     1
19     1
31     1
37     1
61     1
63     1
73     1
85     1
88     1
122     1
123     4
124     4
125     3
126     1
289     4492
290     3887
291     3125
292     2273
293     1525
294     913
295     441
296     152
297     50
298     7
299     1      Could you please through some light on the difference between the compress and the coalesce on the effect they have made on
(a) the number of keys per leaf blocks within my index
(b) the space and size of my index?
Best regards
Mohamed Houri

What is bad # for 'Space Allocated/Used" and 'ITL Waits' in V$SEGMENT_STATS

I ran a query against the V$SEGMENT_STATISTICS view today and got some possibly disturbing numbers. Can some one let me know if they are bad or if I just reading to much into them.
DB has been up since 1/10/2011 so they represent the stats since then. DB size is 3TB
OBJECT_NAME     OBJECT_TYPE     STATISTIC_NAME     VALUE
XXPK0EMIANCE     INDEX     space allocated     27,246,198,784
ITEMINTANCE     TABLE     space allocated     22,228,762,624
LITEMINSTANCE     TABLE     space used     19,497,901,889
XXPK0TEMINSTANCE     INDEX     space used     17,431,957,592
TTINGCORE     TABLE     space allocated     8,724,152,320
XXPK0IANCE     INDEX     space allocated     6,912,212,992
SKISTANCE     TABLE     space allocated     4,697,620,480
IIXCNSTANCE     TABLE     space allocated     4,697,620,480
on the XXPK0EMIANCE index the inital extent is 64k
XXPK0MINSTANCE     INDEX     ITL waits     1,123
XXIEKILSTANCE     INDEX     ITL waits     467
XXPKLINSTANCE     INDEX     ITL waits     463
XXPKCE     INDEX     ITL waits     338
XXIE3ENT     INDEX     ITL waits     237
If these are bad do they impact performance? My understanding is that being wait states, things stop until they are resolved. Is that true.
Also these looked high, are they?
LATION_PK     INDEX     logical reads     242,212,503,104
XXAK1STSCORE     INDEX     logical reads     117,542,351,984
XXPK0TSTANCE     INDEX     logical reads     113,532,240,160
TCORE     TABLE     db block changes 1,913,902,176
SDENT     TABLE     physical reads     72,161,312
XXPK0PDUCT     INDEX     segment scans     35,268,027
ESTSORE     TABLE     buffer busy waits     2,604,947
XXPK0SUCORE     INDEX     buffer busy waits     119,007
XXPK0INSTANCE     INDEX     row lock waits     63,810
XXPK0EMINSTANCE     INDEX row lock waits     58,129
XXPK0NSTANCE     INDEX     row lock waits     57,776
XXIE2DDSTANCE     INDEX     row lock waits     54,788
XXPK0DDDSTSCORE     INDEX row lock waits     49,167
Am i just reading too much into this? I am not a DBA, our DBA is too busy doing data changes and such to spent time looking at these stuff. I was tasked to try to find out why our DB is so slow.

Statistics on waits and reads are cumulative since the last database instance startup --- which was more than 4 months ago.
So :
XXPK0MINSTANCE INDEX ITL waits 1,1231,123 waits in 4+ months isn't bad.
Reading such statistics without reference to the duration is utterly meaningless.
Those 1,123 waits could have been 10 waits a day @1 every 2 hours.
OR those 1,123 waits could have occurred between 01:00 and 01:30 on 03-May-2011.
We have no way of knowing which is the case.
Hemant K Chitale

Reuse of freed space after DELETE statement (ASSM)

Dear Members,
After DELETE of records in tables, the USED SPACE in tablespace still grows when new records are inserted. So the freed space is apparently not reused!
DB is Oracle 9.2. and ASSM is used.
Does anyone knows how to solve this problem?

1) Table (heap) space will continue to grow after deletes if the new rows are appended (APPEND HINT). Appending rows does not reuse free space in existing blocks.
2) Index space will continue to grow after deletes if the leaf blocks could not be reused. Index leaf blocks will be reused only if a) new data index keys will fit in on of the existing leaf blocks that still has entries after the delete completes; b) all of the entries in the leaf block were deleted and a new leaf block needs to be added to the index. It is possible to shrink/coalesce or rebuild an index to cure this phenomenon.

Seqment shrink with function based indexes - 10.2.0.3

I see 10g Rel 2 limiation with function based index while doing segment shrink. Is their a workaround? I tried to drop the function based index before shrink, still shrink is taking several hrs to complete.
Any help is appreciated.
Thanks,
Siva

Hi,
Analogy: suppose you have 1 million barrels filled with water near 85% maybe less, now you spilled ...say 40% the total water, maybe you have 400,000 empty barrels or the equivalent (here comes the overhead) you are going to concentrate the water in 600,000 barrels and return the empty ones to the "Oracle Server" store, just to reclaim them gradually until you have the starting 1 million barrel.
Our advise: keep the objects as they are, both table and index. Oracle will use released space as efficiently as he can, which is (at that level) better than us.
You're worried about the index space? much better leave it now, that's the structure which may cause the major part of overhead.
Regards
Ignacio
http://oracledisect.blogspot.com

Database Configuration: Table space does not exist error

Hi all,
while running Database configuration wizard in Siebel 8.0 installation process I receive the following error:
C103: The table\\index space siebelts entered does not exist in your database.Please ensure you entered the correct table\\
index space.
I have verified the following things:
1) Verified in database that, SIEBELTS tablespace is created but not online.
2) grantusr.sql is executed successfully.SADMIN user and SIEBEL table owner accounts are created.
3) SIEBELTS tablespace is assigned as default tablespace for SADMIN and LDAPUSER. There were no problems running the grantusr.sql.
How can it be that the Wizard shows up this error when the grantusr.sql didn't show it?. The problem is the SIEBELTS. The wizard doesn't find it, but it does find the SIEBELINDEXTS tablespace. Checking the last one, it appears online.

this is what I checked as DBA:
SQL> select * from dba_tablespaces where tablespace_name='SIEBELTS';
TABLESPACE_NAME BLOCK_SIZE INITIAL_EXTENT NEXT_EXTENT MIN_EXTENTS
MAX_EXTENTS PCT_INCREASE MIN_EXTLEN STATUS CONTENTS LOGGING FOR EXTENT_MAN
ALLOCATIO PLU SEGMEN DEF_TAB_ RETENTION BIG
SIEBELTS 8192 65536 1
2147483645 65536 ONLINE PERMANENT LOGGING NO LOCAL
SYSTEM NO AUTO DISABLED NOT APPLY NO
SQL> select * from dba_tablespaces where tablespace_name='SIEBELINDEXTS';
TABLESPACE_NAME BLOCK_SIZE INITIAL_EXTENT NEXT_EXTENT MIN_EXTENTS
MAX_EXTENTS PCT_INCREASE MIN_EXTLEN STATUS CONTENTS LOGGING FOR EXTENT_MAN
ALLOCATIO PLU SEGMEN DEF_TAB_ RETENTION BIG
SIEBELINDEXTS 8192 65536 1
2147483645 65536 ONLINE PERMANENT LOGGING NO LOCAL
SYSTEM NO AUTO DISABLED NOT APPLY NO

Reclaim Disk Space After Deleting Versions.

We've recently went through a few large Document Libraries using Power-Shell and deleted tens of thousands of versions of files we didn't need the version history for.
Unfortunately the DB size has not gotten any smaller. I went in to try and shrink the DB however there is very little available space to reclaim.
Is there something else that needs to be done after versions are deleted to fully release the drive space on our SQL box?

Measuring the MDF/LDF isn't going to be a good calculation. For one, you have padding done by SQL Server itself, then you have index space and other metadata storage, and of course you have all of the information that is associated with the BLOB anyhow.
But with 3 versions of the document, again only the differences are stored, so it wouldn't be 600KB * 3 in that case.
http://blogs.technet.com/b/wbaer/archive/2012/11/12/introduction-to-shredded-storage-in-sharepoint-2013.aspx
Also, why are you wanting to shrink the database? Shrinking destroys the indices and generally degrades performance (e.g. if you encounter another data file expansion).
Trevor Seward
Follow or contact me at...
&nbsp&nbsp
This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

Rebuilding indexes with monotonically increasing sequences

Hi
I have been reading this paper
http://richardfoote.files.wordpress.com/2007/12/index-internals-rebuilding-the-truth.pdf
*On page 91 we have*
CREATE TABLE test_empty_block (id NUMBER, name VARCHAR2(30));
Table created.
INSERT INTO test_empty_block SELECT rownum, 'BOWIE' FROM dual
CONNECT BY level <= 10000;
10000 rows created.
COMMIT;
CREATE INDEX test_empty_block_idx ON test_empty_block(id);
Index created.
On page 92 we have
SQL> DELETE test_empty_block WHERE id between 1 and 9990;
9990 rows deleted.
SQL> COMMIT;
Commit complete.
SQL> ANALYZE INDEX test_empty_block_idx VALIDATE STRUCTURE;
Index analyzed.
SQL> SELECT lf_blks, del_lf_rows FROM index_stats;
LF_BLKS DEL_LF_ROWS
21 9990
On page 93
SQL> INSERT INTO test_empty_block SELECT rownum+20000, 'ZIGGY' FROM dual CONNECT BY level <= 10000;
10000 rows created.
SQL> COMMIT;Commit complete.
SQL> ANALYZE INDEX test_empty_block_idx VALIDATE STRUCTURE;
Index analyzed.
SQL> SELECT lf_blks, del_lf_rows FROM index_stats;
LF_BLKS DEL_LF_ROWS
21 0
when the DEL_LF_ROWS is 0
How come Richard goes on to state that on page 96.
Although deleted index space is generally reusable, there can be wasted space
Monotonically increasing index values and deletions
Edited by: 899881 on Jan 3, 2012 9:05 PM
Edited by: 899881 on Jan 3, 2012 9:06 PM

899881 wrote:
How come Richard goes on to state that on page 96.
Although deleted index space is generally reusable, there can be wasted space
Monotonically increasing index values and deletions
I believe this is addressed in page 103 of the same document you posted a link to.

What do I do after shrink space

Hi,
Do I need to do anything after shrink space?
After I shrink the tables and indexes spaces, I saw the significent space saving. question is do I need to re-collect statistic after shrink? would query plans changed after shink space? if I have outlines defined to freeze query plan, should I re-generated outlines?
anything else should I consider after shrink space?
Thank you

asanga wrote:
no need to do anything for outlinesThank you !. so, this would imply that query plan won't be changed after shrink? is my understanding correct?

Behaviour of Index

I am facing a index issue as described below
My table is a monthly partition table
1 index is bitmap index is local index
Data loading is only direct insert
I am not able to understand why the tree will be imbalanced through a general insert.
The local bitmap index is around 2gb but the each partitions are around 45mb size.But when insert is happening the particular partition of the said index is taking around 2gb space. On analyzing index partition I found the belevel of
that partition to be more than 9
Then I rebuilt the index, and analyzed it again
Sizer came down to 45mb and belevel 1
I want to know why the index is behaving this way
Yachendra

1. Which way of "direct insert" are you using?
2. Are you direct inserting in parallel mode?
Bitmap index generally deals "well" batched dml(eg. insert ... append) - No big space wastage problem.
It seems that you're already using batched dml, but let us make it clear you're adopting a efficient batched dml.
(The bitmap index space management under DML got greatly enhanced in 10g, but you're alreay on 10g)

Recreating Index Behaviour

I have an index which has size 12 GB , i reliazed that this index space is fragmented for that i decided to defragmente its space , what i did for the dfragmentation is as follows.
1) drop that index.
2) recreate the same index.
-Before dropping that index the tablepace of that index space usage was 89 % in Enterprise manager console tablespaces link.
-After dropping this index it reclaimed the space of this tablepace usage column from 89 % to 81 %, i.e it reduce the space to 8%.
-After recreating that index the space did not reuse recliamed space from that tablespace , it reduced the space of /orahome, where my datafiles reside.
Though recreating an index is not having the same space as before , it is occuping the space of 4 GB as before to 10 GB.Why recreating the index is consuming the space of /orahome though the space from index tablespace is reclaimed?

no i am recreating the index on the same tablespace from where i dropped.
This script (metadata) i got from PL/SQL developer before dropping that index , i used the same script after dropping the index.
create unique index WF_ITEM_ATTRIBUTE_VALUES_PK on WF_ITEM_ATTRIBUTE_VALUES (ITEM_TYPE, ITEM_KEY, NAME)
tablespace APPS_TS_TX_IDX
pctfree 10
initrans 11
maxtrans 255
storage
    initial 128K
    next 128K
    minextents 1
    maxextents unlimited
    pctincrease 0
SQL> Drop index WF_ITEM_ATTRIBUTE_VALUES_PK
2 /
Index dropped.
[prod1@uat1 ~]$ df -ha
Filesystem                      Size           Used           Avail           Use%           Mounted on
/dev/mapper/vgora-lvora             1.4T           1.3T             93G           94%           /orahome
SQL> create unique index WF_ITEM_ATTRIBUTE_VALUES_PK on WF_ITEM_ATTRIBUTE_VALUES
2 (ITEM_TYPE, ITEM_KEY, NAME)
3    tablespace APPS_TS_TX_IDX
4    pctfree 10
5    initrans 11
6    maxtrans 255
7    storage
8    (
9      initial 128K
10      next 128K
11      minextents 1
12      maxextents unlimited
13      pctincrease 0
14    );
Index created.
[prod1@uat1 bin]$ df -ha
Filesystem                           Size           Used           Avail           Use%      Mounted on
/dev/mapper/vgora-lvora                     1.4T           1.3T               85G             94%      /orahome

Mutt/Offlineimap Sent mail is showing up in Gmail Inbox

Hi,
I am just starting my journey with mutt and quite like the interface thus far but I am having trouble with sent emails showing up in my Gmail inbox. It is a little annoying to always have my sent emails appear as unread in my inbox. In my search for a solution I have found that this behavior sometimes occurs if you have Gmail filters that are set to never send to spam, I checked and do not have any such filters. This could also happen if I had $record set, but I have specifically unset record. My muttrc and offlineimaprc are as follows (I used several tutorial sites to help create these) (I have hashed out some personal details):
muttrc
# Paths ----------------------------------------------
set folder = ~/.mail # mailbox location
set alias_file = ~/.mutt/alias # where to store aliases
set header_cache = ~/.mutt/cache/headers # where to store headers
set message_cachedir = ~/.mutt/cache/bodies # where to store bodies
set certificate_file = ~/.mutt/certificates # where to store certs
set mailcap_path = ~/.mutt/mailcap # entries for filetypes
set tmpdir = ~/.mutt/temp # where to keep temp files
set signature = ~/.mutt/sig # my signature file
# Basic Options --------------------------------------
set wait_key = no # shut up, mutt
set mbox_type = Maildir # mailbox type
set timeout = 3 # idle time before scanning
set mail_check = 0 # minimum time between scans
unset move # gmail does that
set delete # don't ask, just do
unset confirmappend # don't ask, just do!
set quit # don't ask, just do!!
unset mark_old # read/new is good enough for me
#set beep_new # bell on new mails
set pipe_decode # strip headers and eval mimes when piping
set thorough_search # strip headers and eval mimes before searching
# Status Bar -----------------------------------------
set status_chars = " *%A"
set status_format = "───[ Folder: %f ]───[%r%m messages%?n? (%n new)?%?d? (%d to delete)?%?t? (%t tagged)? ]───%>─%?p?( %p postponed )?───"
# Header Options -------------------------------------
ignore * # ignore all headers
unignore from: to: cc: date: subject: # show only these
unhdr_order * # some distros order things by default
hdr_order from: to: cc: date: subject: # and in this order
# Account Settings -----------------------------------
# Default inbox.
set spoolfile = "+mygmail/INBOX"
# Alternate email addresses.
alternates ####### ########
# Other special folders.
set mbox = "+mygmail/archive"
set postponed = "+mygmail/drafts"
# Index View Options ---------------------------------
set date_format = "%m/%d"
set index_format = "[%Z] %D %-20.20F %s"
set sort = threads # like gmail
set sort_aux = reverse-last-date-received # like gmail
set uncollapse_jump # don't collapse on an unread message
set sort_re # thread based on regex
set reply_regexp = "^(([Rr][Ee]?(\[[0-9]+\])?: *)?(\[[^]]+\] *)?)*"
# Index Key Bindings ---------------------------------
bind index gg first-entry
bind index G last-entry
bind index R group-reply
bind index <tab> sync-mailbox
bind index <space> collapse-thread
# Ctrl-R to mark all as read
macro index \Cr "T~U<enter><tag-prefix><clear-flag>N<untag-pattern>.<enter>" "mark all messages as read"
# Sync email
macro index O "<shell-escape>offlineimap<enter>" "run offlineimap to sync all mail"
macro index o "<shell-escape>offlineimap -qf INBOX<enter>" "run offlineimap to sync inbox"
# Saner copy/move dialogs
macro index C "<copy-message>?<toggle-mailboxes>" "copy a message to a mailbox"
macro index M "<save-message>?<toggle-mailboxes>" "move a message to a mailbox"
# Pager View Options ---------------------------------
set pager_index_lines = 10 # number of index lines to show
set pager_context = 3 # number of context lines to show
set pager_stop # don't go to next message automatically
set menu_scroll # scroll in menus
#set tilde # show tildes like in vim
unset markers # no ugly plus signs
set quote_regexp = "^( {0,4}[>|:#%]| {0,4}[a-z0-9]+[>|]+)+"
alternative_order text/plain text/enriched text/html
# URLview ... calls ~/.urlview
macro pager \Cu <pipe-entry>'urlview'<enter> 'Follow links with urlview'
# Compose View Options -------------------------------
set realname = "My Name" # who am i?
set envelope_from # which from?
set sig_dashes # dashes before sig
set edit_headers # show headers when composing
set fast_reply # skip to compose when replying
set askcc # ask for CC:
set fcc_attach # save attachments with the body
unset mime_forward # forward attachments as part of body
set forward_format = "Fwd: %s" # format of subject when forwarding
set forward_decode # decode when forwarding
set attribution = "On %d, %n wrote:" # format of quoting header
set reply_to # reply to Reply to: field
set reverse_name # reply as whomever it was to
set include # include message in replies
set forward_quote # include message in forwards
set editor = "emacs -nw"
set from = "#################@gmail.com"
set sendmail = "/usr/local/bin/msmtp -a mygmail ###############@gmail.com"
set sendmail_wait = 0
unset record
#color scheme
source muttsolar16
My offlineimaprc
# Sample minimal config file. Copy this to ~/.offlineimaprc and edit to
# get started fast.
[general]
ui = TTY.TTYUI
accounts = MyGmail
pythonfile=~/.mutt/offlineimap.py
fsync = False
[Account MyGmail]
localrepository = CGLocal
remoterepository = CGRemote
status_backend = sqlite
[Repository CGLocal]
type = Maildir
localfolders = ~/.mail/mygmail
nametrans = lambda folder: {'drafts': '[Gmail]/Drafts',
'sent': '[Gmail]/Sent Mail',
'flagged': '[Gmail]/Starred',
'trash': '[Gmail]/Trash',
'archive': '[Gmail]/All Mail',
}.get(folder, folder)
[Repository CGRemote]
maxconnections=1
type = Gmail
remoteuser = ############@gmail.com
remotepasseval = keyring.get_password("Login","############@gmail.com")
realdelete = no
sslcacertfile = /etc/ssl/certs/ca-certificates.crt
nametrans = lambda folder: {'[Gmail]/Drafts': 'drafts',
'[Gmail]/Sent Mail': 'sent',
'[Gmail]/Starred': 'flagged',
'[Gmail]/Trash': 'trash',
'[Gmail]/All Mail': 'archive',
}.get(folder, folder)
folderfilter = lambda folder: folder not in ['[Gmail]/Trash',
'[Gmail]/Important',
'[Gmail]/Spam',
I use msmtp to send the emails (and they do send) but as far as I know that program should have nothing to do with my folder labeling.
What happens exactly: When in mutt, I press 'm' and compose an email and send with 'y'. Oddly enough, the email appears in my gmail inbox (the webmail) even before I sync mutt with offlineimap (I don't automatically sync). Once I sync, I see the email in both my sent mail and inbox.
Any thoughts would be appreciated

You have unset the record variable.

Out of alignment web content created in FW CS6

Hello everyone
I have designed an entire web page in Fireworks CS6, sliced up individual components of the page and exported them as HTML and image. The page displays in Chrome and Firefox beautifully but not in IE9. In IE9, some web content appears out of alingment exposing light blue spacers as below:
Here is a copy of the sourcecode. I am also wondering how you could export a file in HTML5 because it always deafults to XHTML1.0. Any advice would be appreciated.
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">

<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title></title>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">

<link href="css/standard.css" rel="stylesheet" type="text/css" />
</head>
<body bgcolor="#99ccff">
<table width="800" border="0" cellpadding="0" cellspacing="0" bgcolor="#99ccff" style="display: inline-table;" >

<tr>
   <td><img src="images/index/spacer.gif" width="50" height="1" alt=""></td>
   <td><img src="images/index/spacer.gif" width="99" height="1" alt=""></td>
   <td><img src="images/index/spacer.gif" width="100" height="1" alt=""></td>
   <td><img src="images/index/spacer.gif" width="34" height="1" alt=""></td>
   <td><img src="images/index/spacer.gif" width="2" height="1" alt=""></td>
   <td><img src="images/index/spacer.gif" width="31" height="1" alt=""></td>
   <td><img src="images/index/spacer.gif" width="32" height="1" alt=""></td>
   <td><img src="images/index/spacer.gif" width="101" height="1" alt=""></td>
   <td><img src="images/index/spacer.gif" width="68" height="1" alt=""></td>
   <td><img src="images/index/spacer.gif" width="1" height="1" alt=""></td>
   <td><img src="images/index/spacer.gif" width="31" height="1" alt=""></td>
   <td><img src="images/index/spacer.gif" width="71" height="1" alt=""></td>
   <td><img src="images/index/spacer.gif" width="29" height="1" alt=""></td>
   <td><img src="images/index/spacer.gif" width="97" height="1" alt=""></td>
   <td><img src="images/index/spacer.gif" width="3" height="1" alt=""></td>
   <td><img src="images/index/spacer.gif" width="1" height="1" alt=""></td>
   <td><img src="images/index/spacer.gif" width="1" height="1" alt=""></td>
   <td><img src="images/index/spacer.gif" width="49" height="1" alt=""></td>
   <td><img src="images/index/spacer.gif" width="1" height="1" alt=""></td>
</tr>
<tr>
   <td colspan="18"><img name="body" src="images/index/body.jpg" width="800" height="15" alt=""></td>
   <td><img src="images/index/spacer.gif" width="1" height="15" alt=""></td>
</tr>
<tr>
   <td rowspan="12"><img name="index_r2_c1" src="images/index/index_r2_c1.jpg" width="50" height="1040" alt=""></td>
   <td rowspan="3" colspan="5"><img name="index_r2_c2" src="images/index/index_r2_c2.jpg" width="266" height="146" alt=""></td>
   <td colspan="12"><img name="index_r2_c7" src="images/index/index_r2_c7.jpg" width="484" height="5" alt=""></td>
   <td><img src="images/index/spacer.gif" width="1" height="5" alt=""></td>
</tr>
<tr>
   <td rowspan="3" colspan="6"><img name="index_r3_c7" src="images/index/index_r3_c7.jpg" width="304" height="149" alt=""></td>
   <td colspan="2"><img name="index_r3_c13" src="images/index/index_r3_c13.jpg" width="126" height="17" alt=""></td>
   <td rowspan="3" colspan="4"><img name="index_r3_c15" src="images/index/index_r3_c15.jpg" width="54" height="149" alt=""></td>
   <td><img src="images/index/spacer.gif" width="1" height="17" alt=""></td>
</tr>
<tr>
   <td rowspan="2" colspan="2"><img name="index_r4_c13" src="images/index/index_r4_c13.jpg" width="126" height="132" alt=""></td>
   <td><img src="images/index/spacer.gif" width="1" height="124" alt=""></td>
</tr>
<tr>
   <td colspan="5"><img name="index_r5_c2" src="images/index/index_r5_c2.jpg" width="266" height="8" alt=""></td>
   <td><img src="images/index/spacer.gif" width="1" height="8" alt=""></td>
</tr>
<tr>
   <td><a href="index.html" alt="Home"><img name="homebutton" src="images/index/home-button.jpg" width="99" height="29" alt="link to Home"></a></td>
   <td><a href="profile.html" alt="Who We Are"><img name="index_r6_c3" src="images/index/index_r6_c3.jpg" width="100" height="29" alt="link to Who We Are"></a></td>
   <td colspan="4"><a href="vision.html" "Our Vision"><img name="index_r6_c4" src="images/index/index_r6_c4.jpg" width="99" height="29" alt="link to Our Vision"></a></td>
   <td><a href="services.html" alt="link to Our Vision"><img name="index_r6_c8" src="images/index/index_r6_c8.jpg" width="101" height="29" alt="Our Services"></a></td>
   <td colspan="3"><a href="faq.html" alt="FAQ"><img name="index_r6_c9" src="images/index/index_r6_c9.jpg" width="100" height="29" alt="link to FAQ"></a></td>
   <td colspan="2"><a href="contact.html" alt="Contact Us"><img name="index_r6_c12" src="images/index/index_r6_c12.jpg" width="100" height="29" alt="link to contact us"></a></td>
   <td colspan="2"><a href="quote.html"><img name="index_r6_c14" src="images/index/index_r6_c14.jpg" width="100" height="29" alt="link to Get a Quote"></td>
   <td rowspan="4" colspan="3"><img name="index_r6_c16" src="images/index/index_r6_c16.jpg" width="51" height="374" alt=""></td>
   <td><img src="images/index/spacer.gif" width="1" height="29" alt=""></td>
</tr>
<tr>
   <td colspan="14"><img name="index_r7_c2" src="images/index/index_r7_c2.jpg" width="699" height="8" alt=""></td>
   <td><img src="images/index/spacer.gif" width="1" height="8" alt=""></td>
</tr>
<tr>
   <td colspan="10"><img name="index_r8_c2" src="images/index/index_r8_c2.jpg" width="499" height="321" alt=""></td>
   <td colspan="4"><img name="index_r8_c12" src="images/index/index_r8_c12.jpg" width="200" height="321" alt=""></td>
   <td><img src="images/index/spacer.gif" width="1" height="321" alt=""></td>
</tr>
<tr>
   <td colspan="14"><img name="index_r9_c2" src="images/index/index_r9_c2.jpg" width="699" height="16" alt=""></td>
   <td><img src="images/index/spacer.gif" width="1" height="16" alt=""></td>
</tr>
<tr>
   <td colspan="3"><img name="index_r10_c2" src="images/index/index_r10_c2.jpg" width="233" height="249" alt=""></td>
   <td colspan="5"><img name="index_r10_c5" src="images/index/index_r10_c5.jpg" width="234" height="249" alt=""></td>
   <td rowspan="4"><img name="index_r10_c10" src="images/index/index_r10_c10.jpg" width="1" height="512" alt=""></td>
   <td colspan="6"><img name="index_r10_c11" src="images/index/index_r10_c11.jpg" width="232" height="249" alt=""></td>
   <td rowspan="2" colspan="2"><img name="index_r10_c17" src="images/index/index_r10_c17.jpg" width="50" height="250" alt=""></td>
   <td><img src="images/index/spacer.gif" width="1" height="249" alt=""></td>
</tr>
<tr>
   <td colspan="8"><img name="index_r11_c2" src="images/index/index_r11_c2.jpg" width="467" height="1" alt=""></td>
   <td colspan="6"><img name="index_r11_c11" src="images/index/index_r11_c11.jpg" width="232" height="1" alt=""></td>
   <td><img src="images/index/spacer.gif" width="1" height="1" alt=""></td>
</tr>
<tr>
   <td colspan="3"><img name="index_r12_c2" src="images/index/index_r12_c2.jpg" width="233" height="249" alt=""></td>
   <td rowspan="2"><img name="index_r12_c5" src="images/index/index_r12_c5.jpg" width="2" height="262" alt=""></td>
   <td colspan="4"><img name="index_r12_c6" src="images/index/index_r12_c6.jpg" width="232" height="249" alt=""></td>
   <td colspan="7"><img name="index_r12_c11" src="images/index/index_r12_c11.jpg" width="233" height="249" alt=""></td>
   <td rowspan="2"><img name="index_r12_c18" src="images/index/index_r12_c18.jpg" width="49" height="262" alt=""></td>
   <td><img src="images/index/spacer.gif" width="1" height="249" alt=""></td>
</tr>
<tr>
   <td colspan="3"><img name="index_r13_c2" src="images/index/index_r13_c2.jpg" width="233" height="13" alt=""></td>
   <td colspan="4"><img name="index_r13_c6" src="images/index/index_r13_c6.jpg" width="232" height="13" alt=""></td>
   <td colspan="7"><img name="index_r13_c11" src="images/index/index_r13_c11.jpg" width="233" height="13" alt=""></td>
   <td><img src="images/index/spacer.gif" width="1" height="13" alt=""></td>
</tr>
<tr>
   <td colspan="18"><img name="index_r14_c1" src="images/index/index_r14_c1.jpg" width="800" height="145" alt=""></td>
   <td><img src="images/index/spacer.gif" width="1" height="145" alt=""></td>
</tr>
</table>
</body>
</html>
Thank you,
Ead

Excellent. The use of ‘border: none’ in the CSS is a good solution and has been recommended previously in this forum.
As far as HTML5, it isn't natively supported in Fireworks CS6. You could easily replace the DOCTYPE or other metadata within the head of the document by hand, after exporting the HTML; on the other hand, I'm not sure the body of the document really merits it—it's pretty ‘old school’ and possibly contains deprecated features.
This reminds of a thread where a user wanted to edit the HTML Export template:
http://forums.adobe.com/message/4733175
I don't know if they followed through with this or not. It'd be fun to experiment with, but not without backing up all the relevant application files first.
It might instructive for you to try building Fireworks files to be exported as HTML and CSS (choosing ‘CSS and Images’ in the Export dialog), instead of using table-based layouts. This seems possibly more significant than the use of an HTML5 doctype.
http://www.adobe.com/devnet/fireworks/articles/export_css_images.html

Index space

Similar Messages

Maybe you are looking for