pscp - ssh_init: Network error: Cannot assign requested address

Playing around with pscp and encounted with an error

ssh_init: Network error: Cannot assign requested address

it looks like pscp is using port 0 by default and mentioning the port allowed copying the file.

C:\temp>pscp myfie.txt oracle@10.10.10.11:/home/test/
ssh_init: Network error: Cannot assign requested address
C:\temp>
C:\temp>pscp -P 22 myfie.txt oracle@10.10.10.11:/home/test/
The server's host key is not cached in the registry. You
have no guarantee that the server is the computer you
think it is.
The server's ssh-ed25519 key fingerprint is:
ssh-ed25519 255 45:35:11:23:5d:10:e2:e3:60:6a:c9:06:bb:74:ad:34
If you trust this host, enter "y" to add the key to
PuTTY's cache and carry on connecting.
If you want to carry on connecting just once, without
adding the key to the cache, enter "n".
If you do not trust this host, press Return to abandon the
connection.
Store key in cache? (y/n) yes
oracle@10.10.10.11's password:
myfie.txt                 | 0 kB |   0.0 kB/s | ETA: 00:00:00 | 100%
C:\temp>

Extending the partition on my AWS EC2 instance

It's been a while that I was using 8G of space for my little ec2 instance. Today my dad called that his application stopped working and when i logged in I have noticed that the space on EC2 was full. At first instance I have cleared some space and then I thought that it is a time to add more space to the machine.

Adding space was not tough. But there are a few steps. Altough the documentation is clear on AWS but for my reference below was done.

1. Log on to the AWS console and increased teh size to 20G.

2. df -h still showing 8G (Magic will not happen we need to do some work)

$ df -h

Filesystem      Size  Used Avail Use% Mounted on

udev            210M     0  210M   0% /dev

tmpfs            48M  612K   48M   2% /run

/dev/xvda1      7.8G  5.8G  1.6G  80% /

tmpfs           240M     0  240M   0% /dev/shm

tmpfs           5.0M     0  5.0M   0% /run/lock

tmpfs           240M     0  240M   0% /sys/fs/cgroup

tmpfs            48M     0   48M   0% /run/user/1000

$ 

3. Run lsblk to see how the disks are attached and what are the partitions

$ lsblk

NAME    MAJ:MIN RM SIZE RO TYPE MOUNTPOINT

xvda    202:0    0  20G  0 disk 

└─xvda1 202:1    0   8G  0 part /

$

I need to make xvda1 20G

4. Grow partition using 

$ sudo growpart /dev/xvda 1

CHANGED: partition=1 start=16065 old: size=16761118 end=16777183 new: size=41926942,end=41943007

$ 

It grew partition number 1 which is under min to it's full size

5. Note that it is still showing 8G under df -h 

$ df -h

Filesystem      Size  Used Avail Use% Mounted on

udev            210M     0  210M   0% /dev

tmpfs            48M  612K   48M   2% /run

/dev/xvda1      7.8G  5.8G  1.6G  80% /

tmpfs           240M     0  240M   0% /dev/shm

tmpfs           5.0M     0  5.0M   0% /run/lock

tmpfs           240M     0  240M   0% /sys/fs/cgroup

tmpfs            48M     0   48M   0% /run/user/1000

$

6. Just resize the filesystem on partition 

$ sudo resize2fs /dev/xvda1

resize2fs 1.44.1 (24-Mar-2018)

Filesystem at /dev/xvda1 is mounted on /; on-line resizing required

old_desc_blocks = 1, new_desc_blocks = 2

The filesystem on /dev/xvda1 is now 5240867 (4k) blocks long.

$

7. Issue the df -h command and see the size is updated.

$ df -h

Filesystem      Size  Used Avail Use% Mounted on

udev            210M     0  210M   0% /dev

tmpfs            48M  612K   48M   2% /run

/dev/xvda1       20G  5.8G   13G  32% /

tmpfs           240M     0  240M   0% /dev/shm

tmpfs           5.0M     0  5.0M   0% /run/lock

tmpfs           240M     0  240M   0% /sys/fs/cgroup

tmpfs            48M     0   48M   0% /run/user/1000

$

Now I will start paying more money to AWS and have less outages :-) . When you are expanding the partition you can expand it to your need rather that expanding it to full and use the space for something else if you like.

Now my dad will be happy for long time and I do not have to worry regarding sapce for some time.

ORA-3206 signalled during: alter tablespace MYTS add datafile

Getting an error while trying to add a datafile to the tablespace.

ORA-3206 signalled during: alter tablespace MYTS add datafile

SQL> alter tablespace MYTS add datafile '/data/db1/oradata/mydb/myts_02.dbf' size 100M autoextend on maxsize 65536M;
alter tablespace MYTS add datafile '/data/db1/oradata/mydb/myts_02.dbf' size 100M autoextend on maxsize 65536M
*
ERROR at line 1:
ORA-03206: maximum file size of (4194304) blocks in AUTOEXTEND clause is out of range


SQL>



Notice that I am trying to add a datafile with 64G size. This is because my db_block_size = 16384


SQL> show parameter db_block_size

NAME                                 TYPE        VALUE
------------------------------------ ----------- ------------------------------
db_block_size                        integer     16384
SQL>


If you look under
https://docs.oracle.com/cd/E11882_01/server.112/e40402/limits002.htm#REFRN0042

Smallfile (traditional) Tablespaces

Number of blocks

A smallfile tablespace is a traditional Oracle tablespace, which can contain 1022 datafiles or tempfiles, each of which can contain up to approximately 4 million (222) blocks.

222 = 4194304

If you look at the Oracle doc (Doc ID 804733.1)  then it is 4194303

which means that the value should be 
65535.98M

and command will look something like

alter tablespace MYTS add datafile '/data/db1/oradata/mydb/myts_02.dbf' size 100M autoextend on maxsize 65535.98M;


The work around is let oracle determine it and run command below without maxsize value.

SQL> alter tablespace MYTS add datafile '/data/db1/oradata/mydb/myts_02.dbf' size 100M autoextend on;

Tablespace altered.

SQL>